The register/genre-conditional catalogue of how writing fails — a genre map (Tutorial, How-to, Reference, Explanation, Decision, Decision record, Contract/specification, Coaching dialogue), a short list of defects that apply regardless of genre, and an inversion matrix of antipatterns whose correctness depends on…
System-level solution architecture — C4 levels (Context, Container, Component, Code), ArchiMate and UML notations, ADRs, and contracts (OpenAPI/AsyncAPI/LinkML). Use for system and solution design, architecture documentation, and architectural decision-making. Distinct from code structure inside a service (see the…
File what matters into one project's files in a Meaningfy Obsidian vault: at the end of a work session (from the conversation) or at any time from raw call or meeting notes the owner pastes. Writes a dated sessions.md entry, and only what applies to tasks.md, decisions.md, index.md and resources.md; keeps the owner's…
Meaningfy's conventions for notes in a personal Obsidian vault: the folder layout and what each folder holds, the kind of every note and its required properties, the project's standing files, link and tag style, where binaries go, machine-neutral paths, the 00 Inbox/proposed/ staging area, and how a vault session may…
Write today's morning note in a Meaningfy Obsidian vault (04 Daily/YYYY-MM-DD.md, private) from live sources: the calendar, the inbox and sent mail since the previous note, the master to-do list 05 To Do/To-Do.md, this week's plans: keep the master list current (ticks flow back, waiting-on-replies tracked), and create…
Plan and review the owner's objectives in a Meaningfy Obsidian vault across four horizons: year, quarter (OKRs: objectives with measurable key results), month and week: kept in 05 To Do/Objectives YYYY.md with its own change log, and reviewed into 04 Daily/reviews/. Runs a planning session or a review session for one…
Start or close a project folder in a Meaningfy Obsidian vault. new NAME runs the charter gate (five questions, a done a third person could check) and creates 01 Projects/YYYY-MM-DD Name/ (or, for a personal project, 07 Perso/YYYY-MM-DD Name/) with its five standing files; close PROJECT writes the final session entry…
Promote a staged note out of 00 Inbox/proposed/ in a Meaningfy Obsidian vault into a project's artefacts/ or 03 Resources/: after checking it carries kind and every property and section its kind requires, and moving it so every wikilink follows. Refuses and names the missing field when a check fails; never sets the…
Start a work session on one project in a Meaningfy Obsidian vault: read that project's charter (index.md), its latest sessions.md entries, decisions.md and tasks.md, make at most one memory recall naming the project, and summarise where things stand and what is next. It writes nothing except a resources.md row the…
Bootstrap or complete a Meaningfy personal Obsidian vault and its tooling, the way project-setup does for a repository: create the vault layout and its vault-files/ sibling, the templates for every kind, the vault's agent instructions (AGENTS.md with the owner profile and write rules) and the per-CLI permission…
Tidy a Meaningfy Obsidian vault on the owner's request: survey it, present a written plan of every move, merge, rename and delete (and every wikilink each affects), and apply the plan only after an explicit yes, moving so links follow. Invoke explicitly: "tidy my vault", "clean up the inbox", "reorganise these notes"…
Builds and evolves a domain's conceptual model with the user, model-driven and data-centric, choosing the model source and rendering. Use when modelling a domain or evolving an ontology. Not for delegation; not for system architecture (system-architect).
Writes a sendable proposal or offer email from client requirements, asking the questions it needs through its output, with estimate and executive framing. Use when a client asks for an offer. Not for pricing strategy alone (estimation).
Designs a new system with the user before code: use cases, architectural decisions and system diagrams, stating its view and plan briefly before each step. Use when starting or reshaping a system's architecture. Not for delegation; not for code (implementer).
The Meaningfy company voice profile — British English, no em dash, plain current vocabulary, honest and direct, the SMILE values, and the register rule (teach, decide, bind). Use when a skill names meaningfy-voice, or when produced prose must sound like Meaningfy. Trigger on "write this in the Meaningfy voice", "is…
Operates Meaningfy's infrastructure with a person who is not a devops engineer: reads both infra repositories and monitoring, plans each change, gets it reviewed, asks consent with a plain-words card, applies exactly what was shown, verifies and records it. Use when someone opens a session in the stacks repository to…
Reviews one infrastructure change — an OpenSpec change's plan or a PR in either infra repository — against the devops skills and reports findings, blast radius, undo path and stack conformance; read-only. Use when a caller wants the four-eyes review before executing a plan, mid-implementation or before merging. Not…
Watches Meaningfy's infrastructure with no human present: runs the daily check-up, answers alerts with allow-listed operations only when the unattended-action policy says act, parks everything else with a decision card, and reports every run to Slack and GitHub issues. Use when the schedule or an alert fires, or when…
Keeps Meaningfy's Odoo sales pipelines true and moving: grooms deals and contacts with logged, reversible writes, prepares meetings and drafts, and asks the owner only through decision cards. Use when the scheduled open-day, close-day and weekly runs fire, or when the owner opens a sales working or intake session. Not…
Use this skill when you change a server or the infrastructure under the stacks: add a VM, resize, rebuild, sleep or wake one, retire a service, read a terraform plan, write an ansible role or playbook, set the checks of an infrastructure repo, or record and document an operation; it gives the safe-change protocol with…
Use this skill when someone joins or leaves, you rotate a password, use a secret in a command, ask whether a port is exposed, pin GitHub actions, make an emergency change or run an access review on Meaningfy infrastructure; it holds the access, secrets, supply-chain and exposure rules with their levels, the four-eyes…
Use this skill when a company or person Meaningfy deals with must be found, added, researched or profiled in Odoo, before any contact is created, or when a won client's health and outcome need care ("is this person already in our Odoo", "update the profile of X", "find duplicate contacts", "how healthy is our client…
Use this skill when a Meaningfy sales or partner meeting needs a plan, when meeting notes need a same-day follow-up draft, when a deal needs a reply or a quiet one a revival email, or when a client's objection needs an answer ("prepare my meeting with X", "draft the follow-up to the call", "how do I answer this…
Use this skill to run Meaningfy's sales day on its Odoo pipeline: open day, close day, the weekly pipeline review, a working session, or an intake session that brings people from an event or list into Odoo one record at a time ("open the sales day", "close the sales day", "weekly pipeline review", "apply my answers"…
★not rated 2 yesterdayA118 tokens
GPL-3.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: