Cross-cutting basics everyone installs: clear technical writing, explanatory-writing craft, the writing antipatterns catalogue, the Meaningfy company voice, the Meaningfy git/PR workflow, agentic guardrails, how to report a skill or agent problem to skillery, your own rules for agents: load, learn and groom them (rulebook, rule-learner, rule-steward), and working from a repository of house material by its own rules (corpus-repository)
Plugin meaningfy-core from marketplace meaningfy-skillery in meaningfy-ws/skillery. Commands read from the repo's manifest — 3 days ago.
technical-writerThe delivery / developer role: the spine build loop (epic-planning, spec-stewardship, clarity-gate, BDD, code review), clean layered Python (cosmic-python), repo scaffolding (project-setup), CD/deploy (ci-cd-delivery), and the release lifecycle (meaningfy-release)
5 agents
The operations role: provision and change servers as code (infrastructure-operations), run and deploy stacks (stack-operations), monitor, check daily, answer incidents and back up (service-reliability), and keep access and secrets safe (infrastructure-security); with an interactive devops agent, an unattended watch and an infrastructure reviewer
3 agents
The design / modelling role: system architecture (C4, ArchiMate/UML, ADRs, contracts), the living conceptual model, the shared modelling conventions, and the LinkML craft (LinkML → typed artefacts + OWL/SHACL)
2 agents
The commercial role: proposal and offer writing, and estimation
2 agents
The legal role: draft, revise and align contracts and propose clause changes in your own contract repository (contract-practice), with Tolic the lawyer, a lead who works there with you and never sends, signs or registers without your confirmation
1 agent
The advisory role: semantic-technologies coaching, the Decision Package, and executive communication
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.