Praxis
A profession-agnostic Agent Skills OS that interviews how you work, compiles a personalized workflow architecture, and improves it from evidence.
npx -y skills add mfarzanansari/praxis-workflow-os --skill praxisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a person wants to design, install, operate, review, or improve a customized AI-assisted workflow, personal operating system, Obsidian knowledge architecture, or reusable skill system—even when they describe it as productivity, memory, process, SOP, second brain, agent workflow, or "how I work."
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.3 KB, as published. Nobody here has run it
Praxis
Core principle
Route the person to the smallest lifecycle capability that changes the current outcome. Do not load or recreate the whole system for every task.
Praxis treats a workflow as a versioned operating model:
Trigger → Evidence → Decisions → Actions → Deliverable → Verification → Durable learning
Route by lifecycle stage
| Current need | Use |
|---|---|
| Understand the person and their real work | praxis-interview |
| Convert an approved profile into an architecture | praxis-blueprint |
| Create vault files and personalized skills | praxis-setup |
| Preserve useful residue from completed work | praxis-distill |
| Review evidence and improve the operating system | praxis-retrospective |
| Create or evolve a reusable skill | praxis-skill-forge |
| Materialize an approved contract for a named model | Optional prompt-polish companion, when installed or explicitly requested |
When more than one stage is requested, preserve this order:
interview → blueprint approval → setup → real use → distillation → retrospective → skill evolution
Routing procedure
- Inspect the conversation and available artifacts. Reuse facts already known.
- Identify the current lifecycle stage and the deliverable the user expects now.
- Load only the matching skill.
- State the route in one sentence, then execute it.
- When the selected skill reaches an approval gate, stop. Do not silently continue into the next stage.
Optional Prompt Polish handoff
Praxis owns intent, workflow structure, deliverables, quality gates, and human approval boundaries. When those are already approved and the user names a target model, prompt-polish may optionally turn that stable contract into a model-specific execution prompt.
Use the companion only when it is installed or explicitly requested. Pass the approved contract, target model, task form, constraints, and done-condition. Never ask Prompt Polish to invent or redefine the workflow, and never make core Praxis operation depend on it.
Hard gates
- Do not scaffold a workflow before the profile and blueprint are approved.
- Do not create a new skill merely because a task exists once.
- Do not write raw transcripts into durable memory.
- Do not move, rename, delete, or overwrite a person's existing vault by default.
- Do not treat third-party skills as trusted because they are popular.
- Do not automate an action beyond the person's approved risk boundary.
Existing-system mode
When the person already has a vault, prompts, SOPs, or skills:
- inventory what exists;
- infer the current architecture and naming conventions;
- identify strengths worth preserving;
- locate duplication, missing gates, stale references, and retrieval failures;
- propose an augmentation path rather than a replacement.
Completion contract
A routed Praxis task is complete when:
- the correct lifecycle skill was used;
- its artifact or decision was produced;
- unresolved assumptions are visible;
- any required human approval was obtained;
- the next lifecycle stage is named but not automatically executed.
Common routing mistakes
| Mistake | Correction |
|---|---|
| Asking the entire interview in one message | Use praxis-interview; one consequential question per turn. |
| Creating folders before understanding the work | Blueprint and approval first. |
| Building a giant profession persona | Generate a small skill graph from work streams and shared primitives. |
| Saving everything as memory | Distill only future-useful residue. |
| Editing skills based on taste | Use evidence and praxis-skill-forge. |
| Loading every skill “just in case” | Route narrowly; progressive disclosure is part of the architecture. |
See references/lifecycle.md for the artifact contracts between stages.
Gives 0 of the 12 instructions most note taking skills give
Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06
- include a visual element on every slidein 44 of 686, across 13 files
- use wikilinks for internal vault linksin 35 of 686, across 11 files
- commit to a single visual motif across every slidein 34 of 686, across 9 files
- read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
- keep 0.5 inch minimum marginsin 30 of 686, across 7 files
- use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
- re-verify affected slides after every fixin 27 of 686, across 5 files
- run content QA checks before declaring successin 26 of 686, across 3 files
- Use Markdown links for external URLs onlyin 26 of 686, across 10 files
- pick a bold topic specific color palettein 24 of 686, across 2 files
- read editing guide before editing existing presentationsin 23 of 686, across 1 file
- use one dominant color across all slidesin 23 of 686, across 1 file
Said here and by no other author read
- Route to the smallest lifecycle capability that changes the current outcome
- Reuse known facts before invoking a skill
- State the route in one sentence then execute it
- Stop at every approval gate
- Inventory existing systems before augmenting
- Propose augmentation rather than replacement of existing systems
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.