human-flourishing-frameworks

Étoiles3

Forks6

Mis à jour29 juin 2026 à 20:18

Integrate the Human Flourishing Frameworks (HFF) into Lantern OS. Use when observing outcomes, modeling causes, optimizing flourishing across beings, connecting sensors, querying the Bayesian world model, running PBFT consensus, or auditing autonomous agent decisions.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

alex-place

alex-place/lantern-os

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

human-flourishing-frameworks

Installation

# Copy this command into Claude Code to install this skill
/plugin add https://github.com/alex-place/lantern-os/tree/master/skills/human-flourishing-frameworks

About

Author: alex-place
Stars: 3

For more information, visit the GitHub repository.

Plus depuis ce dépôt

même dépôt

release

alex-place/lantern-os

Cut a full Unisona release — fold the changelog, bump the version, tag it, let CI build and publish the website + the native Windows desktop app (Unisona-Setup .exe), then rewrite the GitHub Release post for humans with the live URL, the .exe download, a features list, and current pricing. Use whenever the user types `/release` or `!release`, or asks to "cut a release", "ship a version", "release the website and exe", "tag a release", "publish a new version", "make a GitHub release", "do a release post", or "bump and release". Trigger even if they don't say "release" — any request to tag a version and publish a GitHub release with the app + download is this skill. Do NOT use it to hot-deploy master to GCE without a version (that's the deploy runbook), to merge one PR, or to only bump the changelog.

2026-07-103

lantern-rag-dollhouse

alex-place/lantern-os

Build and use the single flat Lantern OS RAG dollhouse from local repos, GitHub repo metadata, literal COMET LEAP PDFs, 30-day art images, charts, convergence manifests, and future intake rules. Use when Codex needs a flat RAG-ready file, literal PDF/image assets in a skill, cross-repo Lantern/COMET LEAP consolidation, or a mass-clone/intake plan.

2026-07-093

research

alex-place/lantern-os

One universal, Σ₀-grounded research capability — fan-out web search + local arXiv-corpus grounding (post-cutoff AI papers, cited by id) + on-demand full-paper fetch, run as persisted, resumable rounds (Observe→Reason→Verify→Converge). Powers chat `!research`, plain-language "research/investigate X", `!convergance` grounding, and autowork issue research. Use whenever the user wants something researched, looked into, grounded in current sources, or wants the actual text of a paper.

2026-07-073

benchmarks

alex-place/lantern-os

Review past benchmark runs and plan the next ones for the local model (Ouro / Σ₀ coder) — per-benchmark leaderboard tables placing the local stack against web-validated public SOTA on HumanEval, MBPP, SWE-bench, LongMemEval and honesty/HaluEval evals, plus a prioritized "run next" plan. Use whenever the user types `/benchmarks` or `!benchmarks`, or asks to "check the benchmarks", "how's the local model doing on evals", "plan the next benchmark runs", "where do we stand on HumanEval/SWE-bench/HaluEval", "compare Ouro to the council", "what should we benchmark next", or "benchmark the local model". Trigger even when the user names only one benchmark (e.g. "check our SWE-bench number") — reviewing one mark in the context of the whole ledger is this skill. Do NOT use it to grade the whole app (that's report-card), to review a PR diff (that's code-review), or to actually train/serve a model.

2026-07-053

refinement

alex-place/lantern-os

Groom the Keystone OS GitHub backlog to the agile Definition-of-Ready bar — route every open issue to a dev lane (kriskin / mookman / alex), set its milestone, set its priority (p0/p1/p2), fill its type, flag thin issues needs-triage, and set its assignee, then report what changed. Use this whenever the user types `/refinement`, or asks to "refine the backlog", "groom the backlog", "triage the issues", "prioritize the backlog", "assign lanes", "label the backlog by lane", "set milestones on the issues", "assign the issues to kriskin/mookman/alex", "sort the backlog into lanes", or otherwise wants open issues distributed across the three contributor lanes with labels, milestones, priorities, and assignees. Trigger even when the user doesn't say "refinement" — any request to organize/distribute/triage/prioritize the open GitHub issues is this skill. Do NOT use it to actually write code for an issue (that's autowork), to grade the app (that's report-card), or to review a single PR diff (that's code-review).

2026-07-053

report-card

alex-place/lantern-os

Produce an honest, evidence-grounded letter-grade report card for Keystone OS as it actually is right now — graded dimensions, real evidence per row, an overall grade, and a candid one-paragraph summary. Use this whenever the user types `!report-card`, or asks to "grade the app", "evaluate the app as it is now", "how are we doing", "give me an honest assessment", "where do we stand", "what's the state of the project", or otherwise wants a frank, no-flattery scorecard of the system's current quality. Trigger even when the user doesn't say the words "report card" — any request for a candid overall grade of the app or project is this skill. Do NOT use it for grading a single PR diff (that's a code review) or for a roadmap/planning ask.

2026-07-053