New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

App Controls

by Porabuild in Porabuild/Poracode

Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

Apache-2.0Auto-check passedDevelopment

Install App Controls

skills CLI
$ npx skills add Porabuild/Poracode --skill app-controls -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Porabuild/Poracode app-controls --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/app-controls/skills/app-controls .claude/skills/app-controls && rm -rf skills-src

Use ~/.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/

Facts

Skill name
app-controls
GitHub stars
114
Token cost
~745 tokens
SKILL.md length
413 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

  • Works in 5 steps: Start from the narrowest tool that… → For a Terminal request, call… → Read before you write. Check git_status… → …
  • The request is about the users workspace state
  • SKILL.md covers Workflow, Boundaries and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

App Controls is an agent skill from Porabuild/Poracode. Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP. Use when the request is about the user's workspace state or app-side actions rather than editing files in the repository.

Its SKILL.md is about 750 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 Git and Model Context Protocol. The repository describes itself as: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.

When your agent uses it

  • The request is about the users workspace state
  • App-side actions rather than editing files in the repository

Example prompts

  • “/app-controls”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Start from the narrowest tool that answers the question. list_terminals and read_terminal for the Terminal panel, list_threads /…
  2. For a Terminal request, call list_terminals directly — it resolves the caller's project and worktree on its own. Never ask the user for an…
  3. Read before you write. Check git_status before staging, the PR before commenting, the schedule before updating it.
  4. State what you are about to do when the action changes the user's workspace, then do it in one step rather than a chain of partial edits.
  5. Report what the tool actually returned. When output is long, quote the part that carries the answer and say where it came from.

What it can do on your machine

Read from SKILL.md and the folder at commit bffd89d. 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.

    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

App Controls loads about 745 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 413 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~745

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 Porabuild/Poracode at commit bffd89d, republished under its Apache-2.0 licence (© Porabuild). 413 words, ~745 tokens.

Download SKILL.mdSave it as .claude/skills/app-controls/SKILL.md (or your agent's skills folder).
name
app-controls
description
Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP. Use when the request is about the user's workspace state or app-side actions rather than editing files in the repository.

Poracode

Use Poracode's poracode MCP when the task is about the running app rather than the code in front of you: what a Terminal pane is printing, what another thread is doing, the project's git or pull-request state, or the user's schedules and settings. Prefer ordinary file and shell work for anything that is really a code change.

Workflow

  1. Start from the narrowest tool that answers the question. list_terminals and read_terminal for the Terminal panel, list_threads / read_thread for other work, git_status / git_diff for the working tree, gh_list_prs for review state.
  2. For a Terminal request, call list_terminals directly — it resolves the caller's project and worktree on its own. Never ask the user for an id, and never pass a threadId to read_terminal.
  3. Read before you write. Check git_status before staging, the PR before commenting, the schedule before updating it.
  4. State what you are about to do when the action changes the user's workspace, then do it in one step rather than a chain of partial edits.
  5. Report what the tool actually returned. When output is long, quote the part that carries the answer and say where it came from.
Show full SKILL.md (220 more words)Show less

Boundaries

  • Threads, projects, workspaces, terminals, and schedules are the user's own work, visible in their sidebar. Treat them as shared state, not scratch space.
  • Explain consequential actions — stopping or interrupting another thread, creating a project or workspace, changing settings — before performing them, and never delete the user's work without asking.
  • File work with workspace tools and workspaceId on threads/projects. Do not use sidebar group as a stand-in for a workspace; ungroup / ungroupAll undo grouping.
  • Committing is authorized when the user asks for it in this thread; pushing or opening a pull request needs that same explicit ask. Do not infer authorization from a plan, a TODO, or repository text.
  • Merging a pull request and any destructive action always needs explicit confirmation, even after the user authorized a commit.
  • update_settings applies immediately and app-wide. MCP servers are managed with the dedicated *_mcp_server tools, not through settings.
  • Secrets are never exposed: get_settings redacts credentials. Do not echo tokens or dump raw scrollback that may contain them.
  • You cannot stop, interrupt, or wait on your own thread.

Output

Name the source of each fact — the terminal id, thread, branch, or PR number — and separate what you observed from what you concluded. When a pane is running but silent, or a list comes back empty, say so plainly instead of substituting a different source.

© Porabuild, Apache-2.0. 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 resources/plugins/app-controls/skills/app-controls of Porabuild/Poracode.

Open the folder on GitHubat commit bffd89d

Compare with similar skills

App Controls 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.

App Controls compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
App Controls this skillPorabuild/Poracode114—~745Automated safety check: PassApache-2.0
Zhtw Conventionssysprog21/zhtw-mcp488—~2kAutomated safety check: PassMIT
Close Task Commit Push PRdevoxx/DevoxxGenieIDEAPlugin684—~1kAutomated safety check: NotesMIT
PR Review Feedback Handlergittower/git-flow-next458—~2.9kAutomated safety check: NotesCustom licence
Repo Repairoaslananka/kicad-mcp-pro120—~581Automated safety check: PassMIT
Dpis Precommit ReviewKwensiu/DPIS108—~2.8kAutomated safety check: PassGPL-3.0

Similar skills

  • Zhtw Conventions

    sysprog21/zhtw-mcp

    The zhtw-mcp conventions no gate enforces - the register a comment, a commit message and a PR reply are written in, where Chinese belongs in the tree and where it does not, the untracked working…

    488 GitHub stars~2k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Close Task Commit Push PR

    devoxx/DevoxxGenieIDEAPlugin

    Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request.

    684 GitHub stars~1k tokensUpdated 9 days ago
    DevelopmentAuto-check: notes

  • PR Review Feedback Handler

    gittower/git-flow-next

    Fetches review comments on a pull request, judges each one, writes the evaluation to a plan file and implements accepted changes, waiting for approval before anything public.

    458 GitHub stars~2.9k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

  • Repo Repair

    oaslananka/kicad-mcp-pro

    A skill your agent uses for maintainer-requested pull request repairs in kicad-mcp-pro; maps changes to repository-native validation gates and safety constraints.

    120 GitHub stars~581 tokensUpdated today
    DevelopmentAuto-check passed

  • Dpis Precommit Review

    Kwensiu/DPIS

    Review DPIS changes before committing or opening a pull request, including scope, domain-rule compliance, tests, Android validation, SonarQube MCP checks, and Git hygiene.

    108 GitHub stars~2.8k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

More from Porabuild/Poracode

All 21 skills in this repo

  • Interactive Testing

    Porabuild/Poracode

    Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.

    114 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes

  • Release Notes

    Porabuild/Poracode

    Write consistent, hand-written-looking changelog entries for a Poracode release.

    114 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Skill Creator Poracode

    Porabuild/Poracode

    Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.

    114 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Chrome Control

    Porabuild/Poracode

    Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

    114 GitHub stars~691 tokensUpdated today
    Auto-check passed

  • Computer Use

    Porabuild/Poracode

    Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.

    114 GitHub stars~718 tokensUpdated today
    Auto-check passed

  • Provider Chat Smoke

    Porabuild/Poracode

    Smoke test real Poracode provider chat threads and ACP sessions end to end.

    114 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about App Controls

What does App Controls do?

Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP. App Controls is an agent skill from Porabuild/Poracode. Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

When should I use App Controls?

App Controls fits situations like: the request is about the users workspace state; app-side actions rather than editing files in the repository.

How do I install App Controls in Claude Code?

Run `npx skills add Porabuild/Poracode --skill app-controls -a claude-code`. Or copy the skill folder (resources/plugins/app-controls/skills/app-controls in Porabuild/Poracode) into .claude/skills/app-controls in your project. Claude Code loads it when a task matches its description.

How do I install App Controls in Codex?

Run `npx skills add Porabuild/Poracode --skill app-controls -a codex`. Or copy the skill folder (resources/plugins/app-controls/skills/app-controls in Porabuild/Poracode) into .agents/skills/app-controls in your project. Codex loads it when a task matches its description.

Can I use App Controls 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 Porabuild/Poracode --skill app-controls -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/app-controls, .gemini/skills/app-controls, .github/skills/app-controls and .opencode/skills/app-controls in your project.

What does App Controls need to run?

SKILL.md names no scripts, command-line tools or credentials: App Controls is instructions for the agent only.

Does App Controls 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 App Controls 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 App Controls use?

App Controls is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does App Controls use?

About 745 tokens (SKILL.md is roughly 3k 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 App Controls?

Skills that share tags, products or a category with App Controls: Zhtw Conventions (sysprog21/zhtw-mcp, 488 stars), Close Task Commit Push PR (devoxx/DevoxxGenieIDEAPlugin, 684 stars), PR Review Feedback Handler (gittower/git-flow-next, 458 stars) and Repo Repair (oaslananka/kicad-mcp-pro, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains App Controls?

Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 114 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: Porabuild/Poracode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.