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

Bangle Project Operator

by bangle-io in bangle-io/bangle-io

Keep the Bangle 2 GitHub Project aligned with the bangle-io repository.

AGPL-3.0Auto-check passedDevelopment

Install Bangle Project Operator

skills CLI
$ npx skills add bangle-io/bangle-io --skill bangle-project-operator -a claude-code

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

GitHub CLI
$ gh skill install bangle-io/bangle-io bangle-project-operator --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/bangle-io/bangle-io.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/bangle-project-operator .claude/skills/bangle-project-operator && 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
bangle-project-operator
GitHub stars
1.2k
Token cost
~1.4k tokens
SKILL.md length
620 words
Files
4 (incl. scripts, references)
Skills in repo
5
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Keep the Bangle 2 GitHub Project aligned with the bangle-io repository.

  • Works in 7 steps: Read AGENTS.md and run from the… → Inspect live project metadata and… → Inspect relevant repository evidence… → …
  • Completing project items
  • SKILL.md covers Scope, Operate, Create and Update, plus 2 more sections
  • Runs Python scripts from its folder; calls python3 and gh; reaches github.com

What it does

Bangle Project Operator is an agent skill from bangle-io/bangle-io. Keep the Bangle 2 GitHub Project aligned with the bangle-io repository. Use for adding, finding, triaging, prioritizing, scheduling, editing, reconciling, or completing project items; assigning backlog, icebox, sprint, urgency, size, or product-area fields; relating plans, issues, pull requests, and code; auditing whether the board matches repository reality; or requests such as "add a task", "update the board", "triage this", "what should we work on", and "sync the project with the repo".

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/triage.md` and `scripts/bangle_project.py`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: A web only WYSIWYG note taking app that saves notes locally in markdown format. v2: https://app.bangle.io/. The licence is AGPL-3.0.

When your agent uses it

  • Completing project items
  • Assigning backlog
  • Product-area fields
  • Auditing whether the board matches repository reality

Example prompts

  • “add a task”
  • “update the board”
  • “triage this”
  • “/bangle-project-operator”

Requirements

  • Python 3

Workflow steps

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

  1. Read AGENTS.md and run from the repository root.
  2. Inspect live project metadata and candidate items
  3. Inspect relevant repository evidence before deciding what the board should say. Search owning packages, active plans, git history, linked…
  4. Find the existing canonical item by plan number, issue/PR URL or number, exact title, and distinctive keywords. Prefer updating it. Do not…
  5. Decide the minimal mutation. Read references/triage.md for field policy, evidence rules, clarification thresholds, and body formats.
  6. Preview writes with --dry-run, inspect the resolved live option names and target item ID, then rerun without --dry-run. A direct user…
  7. Read the changed item back with inspect --query, then report its title, URL or item ID, fields, evidence, and any unresolved question.

What it can do on your machine

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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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

Bangle Project Operator loads about 1.4k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 130 tokens; SKILL.md has 620 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~130
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.8k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from bangle-io/bangle-io at commit c3310c5, republished under its AGPL-3.0 licence (© bangle-io). 620 words, ~1,401 tokens.

Download SKILL.mdSave it as .claude/skills/bangle-project-operator/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
bangle-project-operator
description
Keep the Bangle 2 GitHub Project aligned with the bangle-io repository. Use for adding, finding, triaging, prioritizing, scheduling, editing, reconciling, or completing project items; assigning backlog, icebox, sprint, urgency, size, or product-area fields; relating plans, issues, pull requests, and code; auditing whether the board matches repository reality; or requests such as "add a task", "update the board", "triage this", "what should we work on", and "sync the project with the repo".

Bangle Project Operator

Treat the Bangle 2 project as the canonical product and engineering backlog. Base every mutation on current board data and repository evidence rather than stale remembered field IDs or guesses.

Scope

  • Organization: bangle-io
  • Repository: bangle-io/bangle-io
  • Project: Bangle 2 (5)
  • Sprint view: https://github.com/orgs/bangle-io/projects/5/views/8
  • Editor slice: https://github.com/orgs/bangle-io/projects/5/views/8?sliceBy%5Bvalue%5D=%F0%9F%93%9D+Editor

Use draft issues for canonical initiatives and work items. Add or edit repository issues only when the user explicitly requests public issue content. Link related issues and pull requests from the canonical draft instead of duplicating the same initiative.

Operate

  1. Read AGENTS.md and run from the repository root.

  2. Inspect live project metadata and candidate items:

    bash
    python3 .codex/skills/bangle-project-operator/scripts/bangle_project.py inspect
python3 .codex/skills/bangle-project-operator/scripts/bangle_project.py inspect --query 'product-area:"📝 Editor" -status:"✅ Done"'

  3. Inspect relevant repository evidence before deciding what the board should say. Search owning packages, active plans, git history, linked issues, and open or merged pull requests. For a full synchronization, also inventory every unfinished plans/*.md file and every open PR.

  4. Find the existing canonical item by plan number, issue/PR URL or number, exact title, and distinctive keywords. Prefer updating it. Do not create a near-duplicate because its title differs.

  5. Decide the minimal mutation. Read references/triage.md for field policy, evidence rules, clarification thresholds, and body formats.

  6. Preview writes with --dry-run, inspect the resolved live option names and target item ID, then rerun without --dry-run. A direct user request to add or update one item authorizes that scoped mutation. Ask before a broad reconciliation that would change multiple items, archive anything, or materially alter product priority or sprint commitments.

  7. Read the changed item back with inspect --query, then report its title, URL or item ID, fields, evidence, and any unresolved question.

Create

Supply all active-item classification fields. Use --iteration current only when work is explicitly scheduled for or active in the current sprint.

bash
python3 .codex/skills/bangle-project-operator/scripts/bangle_project.py create \
  --title "Concise outcome" \
  --body-file /tmp/bangle-project-body.md \
  --status backlog \
  --priority medium \
  --size small \
  --product-area editor \
  --dry-run

The helper discovers the live field IDs and options. It accepts semantic aliases such as P0, urgent, in-progress, tiny, workspace, platform, current, and next.

Update

Resolve the exact project item ID with inspect; never select a write target by fuzzy title alone.

bash
python3 .codex/skills/bangle-project-operator/scripts/bangle_project.py update \
  --item-id PVTI_... \
  --status in-progress \
  --iteration current \
  --dry-run

Use --title or --body-file only for draft items. For repository issues or pull requests, change project fields with this helper and use the appropriate GitHub workflow only when public content edits are in scope. Use --clear-field w to unschedule an item; clearing or moving commitments needs explicit evidence or user direction.

Show full SKILL.md (236 more words)Show less

Reconcile with Repository Reality

  • Treat code, merged/open PR state, issue state, active plans, and explicit maintainer decisions as evidence. Treat titles, unchecked lists, stale bodies, and branch names as leads to verify.
  • Mark work Done only after confirming the delivered outcome, normally through a merged PR or an explicit decision. Record the completion PR or decision in the draft body.
  • Mark work In progress only when implementation has started or an active PR owns it. Record PR readiness and the next action.
  • Keep unstarted but pickup-ready work in Backlog; move work to icebox only for deliberate deferral.
  • Ensure every unfinished repository plan has exactly one canonical draft item. Link related issues/PRs in that item rather than creating competing cards.
  • Preserve useful context when updating bodies. Amend stale sections; do not erase decisions, constraints, recovery concerns, or acceptance criteria merely to make an item shorter.
  • Never implement repository code merely because a board-management request reveals work. Implement only when the user also asks to do the engineering work.

Failure Handling

  • If gh lacks project scope, run gh auth refresh -h github.com -s project and let the user complete authentication.
  • If a write partially succeeds, stop. Report the created or changed item ID and the exact field that failed; do not create a replacement item.
  • If board and repository evidence conflict, preserve both, explain the conflict, and ask only the smallest question needed to choose the authoritative state.

© bangle-io, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in .codex/skills/bangle-project-operator of bangle-io/bangle-io.

  • SKILL.md
  • agents/openai.yaml
  • references/triage.md
  • scripts/bangle_project.py

Open the folder on GitHubat commit c3310c5

Compare with similar skills

Bangle Project Operator 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.

Bangle Project Operator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bangle Project Operator this skillbangle-io/bangle-io1.2k—~1.4kAutomated safety check: PassAGPL-3.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from bangle-io/bangle-io

  • Wordgard

    bangle-io/bangle-io

    Write idiomatic Wordgard editor code (schema elements, extensions, commands, decorations, markdown specs) for the editor-w stack.

    1.2k GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed

  • Bangle Desktop Release

    bangle-io/bangle-io

    Build, test, package, and release the Bangle.io Electron desktop app.

    1.2k GitHub stars~297 tokensUpdated 2 days ago
    Auto-check passed

  • Bangle Followup Operator

    bangle-io/bangle-io

    Operate recurring Bangle.io agent follow-ups after a thread has already started.

    1.2k GitHub stars~991 tokensUpdated 2 days ago
    Auto-check passed

  • Thermonuclear Code Quality Review

    bangle-io/bangle-io

    Perform an unusually strict code-quality audit focused on structural simplification, maintainability, abstraction quality, file growth, branching complexity, type boundaries, architectural…

    1.2k GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Bangle Project Operator

What does Bangle Project Operator do?

Keep the Bangle 2 GitHub Project aligned with the bangle-io repository. Bangle Project Operator is an agent skill from bangle-io/bangle-io. Keep the Bangle 2 GitHub Project aligned with the bangle-io repository.

When should I use Bangle Project Operator?

Bangle Project Operator fits situations like: completing project items; assigning backlog; product-area fields; auditing whether the board matches repository reality.

How do I install Bangle Project Operator in Claude Code?

Run `npx skills add bangle-io/bangle-io --skill bangle-project-operator -a claude-code`. Or copy the skill folder (.codex/skills/bangle-project-operator in bangle-io/bangle-io) into .claude/skills/bangle-project-operator in your project. Claude Code loads it when a task matches its description.

How do I install Bangle Project Operator in Codex?

Run `npx skills add bangle-io/bangle-io --skill bangle-project-operator -a codex`. Or copy the skill folder (.codex/skills/bangle-project-operator in bangle-io/bangle-io) into .agents/skills/bangle-project-operator in your project. Codex loads it when a task matches its description.

Can I use Bangle Project Operator 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 bangle-io/bangle-io --skill bangle-project-operator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bangle-project-operator, .gemini/skills/bangle-project-operator, .github/skills/bangle-project-operator and .opencode/skills/bangle-project-operator in your project.

What does Bangle Project Operator need to run?

Going by SKILL.md and its folder, Bangle Project Operator needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and gh). Our summary lists: Python 3.

Does Bangle Project Operator access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Bangle Project Operator 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Bangle Project Operator use?

Bangle Project Operator is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bangle Project Operator use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Bangle Project Operator?

Skills that share tags, products or a category with Bangle Project Operator: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bangle Project Operator?

bangle-io (a GitHub organization) maintains it in bangle-io/bangle-io, which has 1,233 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 5, 2026.

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