CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

jbaruch/speaker-toolkit

Eleven skills for conference speakers covering rhetoric analysis, talk authoring, deck building and export, CFP submissions, publishing, illustrations, shownotes, and screencast production, informed by a 113-entry Presentation Patterns taxonomy (83 observable: 64 patterns + 19 antipatterns; 30 unobservable: 21 patterns + 9 antipatterns).

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

runtime-repair.mdskills/vault-ingress/references/

Runtime Repair

A repair-only entry into vault-ingress. Another skill's runtime resolver (the shared presentation/publishing skills/shownotes-publisher/scripts/resolve-runtime.py) refused and invoked vault-ingress with a runtime_repair handoff carrying its reason_code, the lane it needs, and the absolute database locator it read. Run only the repair that code names, then finish: never select a batch, reparse, or regenerate anything.

Every read, migration and set_config of this repair targets the handoff's database, with vault_root set to its directory, never the default vault locator. A handoff without database names no target: report that and finish.

reason_codeRepair
database_not_currentthe owner migration, dry run then apply, in the "Schema gate" passage of Bootstrap and Preflight
config_incomplete, interpreter_unusable, interpreter_not_absolute, interpreter_unsupportedrecord an absolute interpreter, at least the Python version check-runtime.py names, that has the toolkit requirements as config.python_path through the owner set_config mutation, per that same passage
runtime_lane_unavailableinstall the toolkit requirements into config.python_path
runtime_lane_unresolvednone to install: the imports never finished probing, which a cold interpreter on a network filesystem does; run the lane check below once to warm it
database_mismatch, database_generation_conflictnone: the vault changed while the resolver read it; report that sync must settle
owner_read_failed, runtime_probe_failed, vault_root_invalid, resolver_failednone: report the resolver's error to the speaker; it carries the owner's remedy when owner_code is present

Confirm an interpreter repair with the lane the handoff names (outline for schema consumers, core for text/export tasks):

"{configured python_path}" "{speaker_toolkit_root}/skills/vault-ingress/scripts/check-runtime.py" \
  --lanes "{lane}" --require-lanes "{lane}"

Report what was repaired, or why nothing was, and return to the caller.

skills

vault-ingress

references

batch-persistence.md

bootstrap-and-preflight.md

catalog-feedback-intake.md

clarification-handoff.md

crop-review.md

end-report.md

entrypoint-failure-contracts.md

known-issues.md

local-media-acquisition.md

markdown-decks.md

pattern-catalog-contract.md

pptx-followup.md

processing-rules.md

queue-selection.md

rhetoric-dimensions.md

runtime-repair.md

sampled-word-evidence.md

schemas-db.md

schemas-obligations.md

source-aliases.md

source-identity-audit.md

source-identity-preflight.md

subagent-instructions.md

video-slide-extraction.md

SKILL.md

README.md

tile.json