personal-ops-assistant
- Repo stars 1
- Author updated Live
- Author repo claude-skills
- Domain
- Productivity
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: personal-ops-assistant
description: Run a lightweight personal operating system by reviewing tasks and notes, clustering priorities…
category: productivity
runtime: no special runtime
---
# personal-ops-assistant output preview
## PART A: Task fit
- Use case: Run a lightweight personal operating system by reviewing tasks and notes, clustering priorities, drafting weekly plans, surfacing risks, and turning messy inputs into clear next actions. Use for weekly reviews, planning sessions, or personal task triage..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Core Workflow / Deliver” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Run a lightweight personal operating system by reviewing tasks and notes, clustering priorities, drafting weekly plans, surfacing risks, and turning messy inputs into clear next actions. Use for weekly reviews, planning sessions, or personal task triage.”.
- **02** When the source has headings, the agent prioritizes “Overview / Core Workflow / Deliver” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Overview / Core Workflow / Deliver”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: personal-ops-assistant
description: Run a lightweight personal operating system by reviewing tasks and notes, clustering priorities…
category: productivity
source: 00PrabalK00/claude-skills
---
# personal-ops-assistant
## When to use
- Run a lightweight personal operating system by reviewing tasks and notes, clustering priorities, drafting weekly plans…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Core Workflow / Deliver” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "personal-ops-assistant" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Core Workflow / Deliver
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Personal Ops Assistant
Overview
Turn a pile of tasks and notes into a realistic plan that can actually be followed.
Core Workflow
- Gather the current tasks, notes, deadlines, and loose commitments.
- Cluster work by theme, urgency, energy level, or strategic importance.
- Choose the small set of priorities that matter most for the current week or planning window.
- Convert priorities into concrete next actions, time blocks, and deferred items.
- Surface risks, overload signals, and tradeoffs so the plan stays credible.
Deliver
- Provide a short summary, top priorities, and next actions.
- Make the plan practical enough to use immediately.
- Keep deferred or dropped items visible so nothing disappears silently.
Guardrails
- Bias toward realism over optimism.
- Keep the number of active priorities small.
- Call out when the workload exceeds the available time.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review