github-mobile-ops
Skill0 starsChanged 4 months agoMITView on GitHub
Explain a phone-first GitHub workflow using Issues as canonical task state, Projects as the operator view, GitHub Mobile as the control surface, and chat as the fast signal path. Use when the user asks how GitHub should work from a phone or lightweight operator surface.
In this repository37 other files it gives its agents.
- adr-logSkill
- adversarial-reviewSkill
- ai-writing-detoxSkill
- autonomous-video-pipelineSkill
- browser-tutorial-videoSkill
- codex-execution-packSkill
- continuity-ledgerSkill
- github-seoSkill
- idea-validationSkill
- illustration-promptSkill
- issue-control-loopSkill
- justdoitSkill
- lazy-seniorSkill
- long-context-dispatchSkill
- openclaw-councilSkill
- parallel-worktreesSkill
- playwrightSkill
- product-councilSkill
- product-shapingSkill
- public-artifact-laneSkill
- readme-generatorSkill
- screenshotSkill
- session-to-postSkill
- spec-bundleSkill
- spreadsheetSkill
- spreadsheet-tabular-analysisSkill
- spreadsheet-xlsx-editSkill
- tool-scoutSkill
- transcribe-basicSkill
- transcribe-diarizeSkill
- transcribeSkill
- triage-findingSkill
- video-builderSkill
- video-render-runSkill
- video-spec-builderSkill
- visual-explainerSkill
- work-shapingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not use when: the real task is coding, repo planning, or a generic GitHub tutorial that does not depend on phone-first operation.
- Very specific: line 17
Start from the split: Issue is canonical task truth, Project is the workflow board, GitHub Mobile is the phone control surface, and chat is …
- Distinctive: line 22
Do not claim the phone replaces the laptop for real coding or deep review.
- Distinctive: line 23
Do not blur GitHub Mobile, Copilot features, Telegram/OpenClaw, and local execution into one fake surface.
- Very specific: line 29
If needed, a minimal project field set such as Status, Priority, Owner, Next action, Blocked, and Due date.
≈ “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
GitHub Mobile Ops
Metadata
- Trigger when: the user wants a mobile-first control loop for GitHub Issues, Projects, and GitHub Mobile.
- Do not use when: the real task is coding, repo planning, or a generic GitHub tutorial that does not depend on phone-first operation.
Skill Purpose
Map GitHub’s mobile surfaces into a clean operator model so the user can control work from a phone without pretending the phone is a full development environment.
Instructions
- Start from the split:
Issueis canonical task truth,Projectis the workflow board,GitHub Mobileis the phone control surface, and chat is the fast signal path. Build the advice around that split instead of mixing responsibilities. - Recommend the smallest honest phone workflow that fits the request. If the user wants field-level guidance or the fuller operator pattern, read
~/.codex/skills/github-mobile-ops/references/mobile-control-surface.md. - Return a concrete operating setup: what lives in the issue, what lives in the project, which fields matter on mobile, and what still needs a laptop.
Non-Negotiable Acceptance Criteria
- Do not claim the phone replaces the laptop for real coding or deep review.
- Do not blur GitHub Mobile, Copilot features, Telegram/OpenClaw, and local execution into one fake surface.
- The recommendation stays concrete: fields, flows, and operator responsibilities beat platform hype.
- Language stays operator-level and plain.
Output
- A compact recommended split between issue, project, mobile app, and chat.
- If needed, a minimal project field set such as
Status,Priority,Owner,Next action,Blocked, andDue date. - A short note about what still requires a laptop or fuller desktop workflow.
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.