How do I install the Github Mobile Ops skill?

Run npx skillmds@latest add kiku-jw/github-mobile-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Mobile Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Mobile Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Mobile Ops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Mobile Ops?

kiku-jw (@kiku-jw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Mobile Ops by kiku-jw — Agent Skill

Name: Github Mobile Ops
Author: kiku-jw

Github Mobile Ops

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.

kiku-jw b8ca53d 3 files · 3.4 KB Updated Sep 17, 2026

File contents

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: Issue is canonical task truth, Project is the workflow board, GitHub Mobile is 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, and Due date.
A short note about what still requires a laptop or fuller desktop workflow.

---name: github-mobile-opsdescription: 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.---# 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 PurposeMap 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.## Instructions1. Start from the split: `Issue` is canonical task truth, `Project` is the workflow board, `GitHub Mobile` is the phone control surface, and chat is the fast signal path. Build the advice around that split instead of mixing responsibilities.2. 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`.3. 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`, and `Due date`.- A short note about what still requires a laptop or fuller desktop workflow.

Frequently asked questions