collaboration-panel
Skill1 starsChanged 2 months agoApache-2.0View on GitHub
Work through GitHub issues assigned to you and PRs requesting your review via the harness collaboration-panel and organisation identity.
In this repository25 other files it gives its agents.
- agent-runtimeSkill
- ball-alignSkill
- canvas-clientSkill
- checkSkill
- chip-designerSkill
- debug-bemuSkill
- debug-compilerSkill
- debug-p2eSkill
- debug-performanceSkill
- debug-verilatorSkill
- domain-modelingSkill
- graph-contractSkill
- grillingSkill
- grill-with-docsSkill
- ip-designerSkill
- model-optimizeSkill
- model-portSkill
- model-recipeSkill
- plugin-verifySkill
- programming-principlesSkill
- repo-installSkill
- reportSkill
- role-identitySkill
- waveformSkill
- workload-testsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Prefer the sidebar 协作面板. Opening it while logged out starts GitHub device login in the panel (no chat tool).
- Very specific: line 17
After reading a PR/issue in the panel, do the real work in the matching workspace repo (ensure_repo when needed).
- Distinctive: line 18
Read-only: never claim GitHub write through this plugin.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
协作面板
When
User asks about assigned issues, review requests, or "任务面板" / PR board for organisation-managed repos.
Workflow
- Prefer the sidebar 协作面板. Opening it while logged out starts GitHub device login in the panel (no chat tool).
- Scope is only repos from organisation config. Do not query other remotes.
- Issues: you are assignee. PRs: you are requested_reviewer. Open only.
- After reading a PR/issue in the panel, do the real work in the matching workspace repo (
ensure_repowhen needed). Quality gates stay with harness skills, not this panel. - Read-only: never claim GitHub write through this plugin.
Fail loud
Auth and API failures must be visible. Do not invent empty success.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.