ai-six-sigma-property-os
<skill_contract> <input>Named property-service workflow, actors, evidence, CTQs, approval boundaries, and MVP constraints.</input> <output>A bounded ontology, DMAIC control plan, agent roles, gates, metrics, and rollback-ready MVP design.</
Reading sources and marking what holds up
What it does
<skill_contract> <input>Named property-service workflow, actors, evidence, CTQs, approval boundaries, and MVP constraints.</input> <output>A bounded ontology, DMAIC control plan, agent roles, gates, metrics, and rollback-ready MVP design.</output> <done>Every proposed state transition and CTQ has an owner, evidence
Read more
source, verifier, approval gate, and control receipt.</done> <non_goals>Full ERP replacement, autonomous safety or pricing decisions, and automation of undefined processes.</non_goals>
Use when property-service operations need an AI plus ontology plus DMAIC design for work orders, dispatch, quotes, evidence, CTQ metrics,…
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
No script files in its folder
Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.
How we know
Listed the 2 files in the skill’s folder on GitHub; none is a script or program.
No known risk pattern found
Launch7’s automated check read all 2 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-04, commit 5a64514 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to Mark393295827/third-brain-v7-skills: 2026-09-19 (15 days before the scan).
Read automatically from the skill’s own files on GitHub on 4 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from Mark393295827
All from this publisher →- agent-teams-command
<skill_contract> <input>A mission with independently ownable workstreams, time SLA requirements, pre-flight task list, token budget, interfaces, permissions, and an integration owner.</input> <output>An isolated worker fleet (5 to 100+ agen
- anthropic-os
<skill_contract> <input>One owned work system with its workflow, users, traces, permissions, metrics, constraints, and review horizon.</input> <output>A supervised operating-system redesign with one bounded experiment, control gates, cadenc
- graph-engineering
<skill_contract> <input>A dependency-heavy objective with candidate nodes, data schemas, owners, effects, verifiers, joins, budgets, and durable state paths.</input> <output>A validated static DAG contract with typed edges, explicit joins,
- harness-engineering
<skill_contract> <input>An agent workflow, runtime environment, tools, data sensitivity, effects, cadence, risk, and operator constraints.</input> <output>An auditable runtime kernel with scoped permissions, scheduling, observability, recov
- loop-engineering
<skill_contract> <input>A repeatable task with inspectable state, finite budgets, permissions, and an independent verifier.</input> <output>A validated Trigger -> Execute -> Verify -> State contract plus resumable run receipts.</output> <do
