Ga naar hoofdinhoud

5 berichten getagd met "Hermiq"

Laat alle tags zien

Hermiq skills tutorial series — Part 2: Qualifying a skill (L1–L7)

· 9 minuten leestijd
Conduction
Open-source workspace stack

Every skill row in the Hermiq catalog carries a badge of seven dots. In this part you learn what the dots mean, run the Qualify action to earn them mechanically, read the scorecard that explains every failure, and attest level 4 as a human curator. You also learn why the ladder deliberately gets harder to climb from level 5 on.

Hermiq skills tutorial series — Part 1: Skills for your agents

· 10 minuten leestijd
Conduction
Open-source workspace stack
Also useful first — the Claude Skills tutorial series

Hermiq skills use the same idea as Claude Code skills: a Markdown document that teaches an agent one capability. If the concept is new to you, part 1 of the Claude Skills series (10 minutes) is a good primer. This series stands on its own, though.

A Hermiq agent gets new capabilities through skills: Markdown documents in the open agentskills.io format, stored as OpenRegister objects. In this part you browse the skills catalog, read the anatomy of the seeded example skills, install one onto an agent, and author your own skill twice: once by hand in the markdown form, once in conversation with the seeded skill-creator skill.

Hermiq skills tutorial series — Part 3: Measuring skills with paired evals

· 9 minuten leestijd
Conduction
Open-source workspace stack

A skill that "feels right" can still add nothing, or make the agent worse. Paired evals answer the question with two runs of the same cases: one with the skill, one without. In this part you use the seeded woo-triage-paired-eval dataset to run a paired baseline against woo-request-triage, read the delta, and watch the L5 evidence appear where Part 2 left a named gap.

Hermiq skills tutorial series — Part 4: Skills that learn

· 11 minuten leestijd
Conduction
Open-source workspace stack

A self-improving skill sounds like a skill that edits itself. In Hermiq it is the opposite: every improvement is a draft that must survive a content scan, an eval gate, and your explicit approval before it becomes a new version. In this final part you read the learnings the seeded tender-summary skill has captured, review its pending improvement draft, decide it, and learn the version history, rollback, and republish surfaces that keep the whole loop reversible.