10 files · 64.5 KB · previews are generated at approval and never executed

• agency-graphic-designer/LICENSEtext · 33.7 KB · preview truncated

                      GNU AFFERO GENERAL PUBLIC LICENSE
                         Version 3, 19 November 2007
  
   Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
   Everyone is permitted to copy and distribute verbatim copies
   of this license document, but changing it is not allowed.
  
                              Preamble
  
    The GNU Affero General Public License is a free, copyleft license for
  software and other kinds of works, specifically designed to ensure
  cooperation with the community in the case of network server software.
  
    The licenses for most software and other practical works are designed
  to take away your freedom to share and change the works.  By contrast,
  our General Public Licenses are intended to guarantee your freedom to
  share and change all versions of a program--to make sure it remains free
  software for all its users.
  
    When we speak of free software, we are referring to freedom, not
  price.  Our General Public Licenses are designed to make sure that you
  have the freedom to distribute copies of free software (and charge for
  them if you wish), that you receive source code or can get it if you
  want it, that you can change the software or use pieces of it in new
  free programs, and that you know you can do these things.
  
    Developers that use our General Public Licenses protect your rights
  with two steps: (1) assert copyright on the software, and (2) offer
  you this License which gives you legal permission to copy, distribute
  and/or modify the software.
  
    A secondary benefit of defending all users' freedom is that
  improvements made in alternate versions of the program, if they
  receive widespread use, become available for other developers to
  incorporate.  Many developers of free software are heartened and
  encouraged by the resulting cooperation.  However, in the case of
  software used on network servers, this result may fail to come about.
  The GNU General Public License permits making a modified version and
  letting the public access it on a server without ever releasing its
  source code to the public.
  
    The GNU Affero General Public License is designed specifically to
  ensure that, in such cases, the modified source code becomes available
  to the community.  It requires the operator of a network server to
  provide the source code of the modified version running there to the
  users of that server.  Therefore, public use of a modified version, on
  a publicly accessible server, gives the public access to the source
  code of the modified version.
  
    An older license, called the Affero General Public License and
  published by Affero, was designed to accomplish similar goals.  This is
  a different license, not a version of the Affero GPL, but Affero has
  released a new version of the Affero GPL which permits relicensing under
  this license.
  
    The precise terms and conditions for copying, distribution and
  modification follow.
  
                         TERMS AND CONDITIONS
  
    0. Definitions.
  
    "This License" refers to version 3 of the GNU Affero General Public License.
  
    "Copyright" also means copyright-like laws that apply to other kinds of
  works, such as semiconductor masks.
  
    "The Program" refers to any copyrightable work licensed under this
  License.  Each licensee is addressed as "you".  "Licensees" and
  "recipients" may be individuals or organizations.
  
    To "modify" a work means to copy from or adapt all or part of the work
  in a fashion requiring copyright permission, other than the making of an
  exact copy.  The resulting work is called a "modified version" of the
  earlier work or a work "based on" the earlier work.
  
    A "covered work" means either the unmodified Program or a work based
  on the Program.
  
    To "propagate" a work means to do anything with it that, without
  permission, would make you directly or secondarily liable for
  infringement under applicable copyright law, except executing it on a
  computer or modifying a private copy.  Propagation includes copying,
  distribution (with or without modification), making available to the
  public, and in some countries other activities as well.
  
    To "convey" a work means any kind of propagation that enables other
  parties to make or receive copies.  Mere interaction with a user through
  a computer network, with no transfer of a copy, is not conveying.
  
    An interactive user interface displays "Appropriate Legal Notices"
  to the extent that it includes a convenient and prominently visible
  feature that (1) displays an appropriate copyright notice, and (2)
  tells the user that there is no warranty for the work (except to the
  extent that warranties are provided), that licensees may convey the
  work under this License, and how to view a copy of this License.  If
  the interface presents a list of user commands or options, such as a
  menu, a prominent item in the list meets this criterion.
  
    1. Source Code.
  
    The "source code" for a work means the preferred form of the work
  for making modifications to it.  "Object code" means any non-source
  form of a work.
  
    A "Standard Interface" means an interface that either is an official
  standard defined by a recognized standards body, or, in the case of
  interfaces specified for a particular programming language, one that
  is widely used among developers working in that language.
  
    The "System Libraries" of an executable work include anything, other
  than the work as a whole, that (a) is included in the normal form of
  packaging a Major Component, but which is not part of that Major
  Component, and (b) serves only to enable use of the work with that
  Major Component, or to implement a Standard Interface for which an
  implementation is available to the public in source code form.  A
  "Major Component", in this context, means a major essential component
  (kernel, window system, and so on) of the specific operating system
  (if any) on which the executable work runs, or a compiler used to
  produce the work, or an object code interpreter used to run it.
  
    The "Corresponding Source" for a work in object code form means all
  the source code needed to generate, install, and (for an executable
  work) run the object code and to modify the work, including scripts to
  control those activities.  However, it does not include the work's
  System Libraries, or general-purpose tools or generally available free
  programs which are used unmodified in performing those activities but
  which are not part of the work.  For example, Corresponding Source
  includes interface definition files associated with source files for
  the work, and the source code for shared libraries and dynamically
  linked subprograms that the work is specifically designed to require,
  such as by intimate data communication or control flow between those
  subprograms and other parts of the work.
  
    The Corresponding Source need not include anything that users
  can regenerate automatically from other parts of the Corresponding
  Source.
  
    The Corresponding Source for a work in source code form is that
  same work.
  
    2. Basic Permissions.
  
    All rights granted under this License are granted for the term of
  copyright on the Program, and are irrevocable provided the stated
  conditions are met.  This License explicitly affirms your unlimited
  permission to run the unmodified Program.  The output from running a
  covered work is covered by this License only if the output, given its
  content, constitutes a covered work.  This License acknowledges your
  rights of fair use or other equivalent, as provided by copyright law.
  
    You may make, run and propagate covered works that you do not
  convey, without conditions so long as your license otherwise remains
  in force.  You may convey covered works to others for the sole purpose
  of having them make modifications exclusively for you, or provide you
  with facilities for running those works, provided that you comply with
  the terms of this License in conveying all material for which you do
  not control copyright.  Those thus making or running the covered works
  for you must do so exclusively on your behalf, under your direction
  and control, on terms that prohibit them from making any copies of
  your copyrighted material outside their relationship with you.
  
    Conveying under any other circumstances is permitted solely under
  the conditions stated below.  Sublicensing is not allowed; section 10
  makes it unnecessary.
  
    3. Protecting Users' Legal Rights From Anti-Circumvention Law.
  
    No covered work shall be deemed part of an effective technological
  measure under any applicable law fulfilling obligations under article
  11 of the WIPO copyright treaty adopted on 20 December 1996, or
  similar laws prohibiting or restricting circumvention of such
  measures.
  
    When you convey a covered work, you waive any legal power to forbid
  circumvention of technological measures to the extent such circumvention
  is effected by exercising rights under this License with respect to
  the covered work, and you disclaim any intention to limit operation or
  modification of the work as a means of enforcing, against the work's
  users, your or third parties' legal rights to forbid circumvention of
  technological measures.
  
    4. Conveying Verbatim Copies.
  
    You may convey verbatim copies of the Program's source code as you
  receive it, in any medium, provided that you conspicuously and
  appropriately publish on each copy an appropriate copyright notice;
  keep intact all notices stating that this License and any
  non-permissive terms added in accord with section 7 apply to the code;
  keep intact all notices of the absence of any warranty; and give all
  recipients a copy of this License along with the Program.
  
    You may charge any price or no price for each copy that you convey,
  and you may offer support or warranty protection for a fee.
  
    5. Conveying Modified Source Versions.
  
    You may convey a work based on the Program, or the modifications to
  produce it from the Program, in the form of source code under the
  terms of section 4, provided that you also meet all of these conditions:
  
      a) The work must carry prominent notices stating that you modified
      it, and giving a relevant date.
  
      b) The work must carry prominent notices stating that it is
      released under this License and any conditions added under section
      7.  This requirement modifies the requirement in section 4 to
      "keep intact all notices".
  
      c) You must license the entire work, as a whole, under this
      License to anyone who comes into possession of a copy.  This
      License will therefore apply, along with any applicable section 7
      additional terms, to the whole of the work, and all its parts,
      regardless of how they are packaged.  This License gives no
      permission to license the work in any other way, but it does not
      invalidate such permission if you have separately received it.
  
      d) If the work has interactive user interfaces, each must display
      Appropriate Legal Notices; however, if the Program has interactive
      interfaces that do not display Appropriate Legal Notices, your
      work need not make them do so.
  
    A compilation of a covered work with other separate and independent
  works, which are not by their nature extensions of the covered work,
  and which are not combined with it such as to form a larger program,
  in or on a volume of a storage or distribution medium, is called an
  "aggregate" if the compilation and its resulting copyright are not
  used to limit the access or legal rights of the compilation's users
  beyond what the individual works permit.  Inclusion of a covered work
  in an aggregate does not cause this License to apply to the other
  parts of the aggregate.
  
    6. Conveying Non-Source Forms.
  
    You may convey a covered work in object code form under the terms
  of sections 4 and 5, provided that you also convey the
  machine-readable Corresponding Source under the terms of this License,
  in one of these ways:
  
      a) Convey the object code in, or embodied in, a physical product
      (including a physical distribution medium), accompanied by the
      Corresponding So

• agency-graphic-designer/README.mdmarkdown · 6.8 KB

  Graphic Designer (Hermes Agency profile)

  agency-graphic-designer is one profile distribution from the Hermes Agency pack by Kyle French. This archive carries that single profile, so it can be installed and read on its own without pulling in the other 112 Agency profiles.

  What the profile does

  A 2D communication graphics specialist. It turns an approved brief and brand/creative direction into composed deliverables: social cards, diagrams, posters, one-pagers, presentation visuals, campaign assets and layout systems — including the production files and exports needed to ship them in print or digital channels.

  Ownership boundaries

  Owns: 2D graphic composition and layout; campaign and social assets; diagrams, posters and presentation graphics; typographic and image hierarchy and format adaptation inside an approved brand system; production files and exports.

  Does not own: the brand identity system (that is Brand Designer) or original art direction across a campaign (Art Director / Creative Director). When a task crosses a boundary, SOUL.md directs the profile to complete the part inside its specialty and hand the adjacent decision to the named owner with evidence and context — rather than quietly expanding scope.

  Capabilities

  Each directory under skills/ is a repeatable procedure, not an alternate persona:

  Skill	Use it for
  graphic-composition	Building a graphic from hierarchy, grid, typography, imagery, whitespace, focal path and channel constraints.
  campaign-asset-production	Producing a coherent family of campaign/social assets across formats while preserving concept and brand recognition.
  diagram-visual-design	Explanatory diagrams: relationships, flow, hierarchy, architecture, process.
  presentation-visual-system	A reusable presentation system: grid, title/body hierarchy, charts, callouts, section transitions, dense-content patterns.
  production-export-preflight	Preflight and export for print or digital: dimensions, resolution, colour mode/profile, bleed and safe areas, fonts, transparency, compression, naming, source preservation.
  academy-continuing-education	The Continuing Education entry point (see below). Preloaded by distribution.yaml.

  Install

  hermes profile install ./agency-graphic-designer --alias --yes
  hermes profile describe agency-graphic-designer \
    --text "Produces composed 2D communication graphics such as social cards, diagrams, posters, one-pagers, presentation visuals, campaign assets, and layout systems from approved brand and creative direction."
  

  --alias registers the profile under the name agency-graphic-designer. Requires a Hermes Agent build that provides hermes profile install.

  Continuing Education dependency

  distribution.yaml declares preload_skills: [academy-continuing-education], and that capability ships inside this archive (skills/academy-continuing-education/), so the preload resolves locally. The wider Continuing Education flow — asking the profile to go learn a capability and saving it with /learn — additionally needs a Hermes build with goal_manage, profile-distribution preload_skills support and bounded goal-judge feedback. Nothing else in the profile depends on it.

  Contents

  Path	What it is
  SOUL.md	The behavioural contract: role, responsibilities, authority and handoff boundaries, working standard, collaboration, definition of done.
  distribution.yaml	Distribution metadata: name, version, description, author, licence, preload_skills.
  skills/	The six procedures above.
  README.md, LICENSE	Added when this single-profile archive was packaged (see provenance).

  The pack is source artifacts only: no credentials, tokens, memory, sessions, logs or generated runtime state.

  Licence and provenance

  AGPL-3.0-only. Author: Kyle French. Upstream: github.com/Dadmin88/hermes-profile-packs, pinned at commit 3821183d2b7d (2026-09-15), profile directory hermes-agency/profiles/agency-graphic-designer. This README.md and LICENSE are the only files in the archive that are not byte-identical to that commit.

  ---

  TalentDelta provenance record (added at packaging)

  • Packaged for: TalentDelta catalogue (draft; gated by review)
  • Upstream: https://github.com/Dadmin88/hermes-profile-packs
  • Pinned commit: 3821183d2b7d5af3cd18bc1c7c4da58ad9bb784e (2026-09-15)
  • Licence: AGPL-3.0-only - AGPL-3.0-only, declared in distribution.yaml; the upstream licence text was copied into this archive as LICENSE rather than shipped from the repository root (see the changes line)
  • Upstream author credit: Kyle French
  • Runtime: Hermes Agent profile distribution: hermes profile install <dir> --alias --yes. No model or provider is pinned. The Continuing Education flow additionally needs a Hermes build with goal_manage and profile-distribution preload_skills support; the preloaded capability itself ships inside this pack
  • Changes made at packaging: this section was appended to README.md. No upstream path is excluded. Added at packaging, not present in the pinned commit: README.md, LICENSE (pack usage notes written for this distribution, and the AGPL-3.0 licence text copied verbatim from the same pinned repository so the archive carries its own licence). Every other file is byte-identical to the pinned commit.
  • Safety read of the packaged archive (packaging time, 2026-10-06): no secrets, credentials, runtime state or sessions - the archive is source only (SOUL.md, distribution.yaml, six capability skills, README.md, LICENSE).

  Packaging notes (TalentDelta)

  • The reviewer-side inspector flags skills/production-export-preflight/SKILL.md as referencing assets/fonts. That string is prose inside the procedure's own inspection checklist ('inspect linked assets/fonts'): it names a workspace the designer inspects at run time, not a file the profile ships. It was left untouched, and the pack's complete file list is SOUL.md, distribution.yaml, the six skills under skills/, README.md and LICENSE.
  • Why this profile: it is the graphic-design role out of 113 sibling profiles. Adjacent roles exist upstream (brand designer, print designer, social designer, design systems, art director, creative director) and are deliberately not bundled here.
  • distribution.yaml declares preload_skills: [academy-continuing-education], and that capability ships INSIDE this archive, so the preload resolves locally with no cross-pack dependency.
  • distribution.yaml also carries requiredHermes: goal_manage, requiredCapabilities: [goal_manage] and the upstream requirements marker for a profile-distribution preload_skills implementation. Those are Hermes build capabilities, not shipped files: on a build without them the Continuing Education flow is inert while the rest of the profile runs.
• agency-graphic-designer/SOUL.mdmarkdown · 2.8 KB

  Graphic Designer

  Role

  You are the Graphic Designer in Hermes Agency. Produces composed 2D communication graphics such as social cards, diagrams, posters, one-pagers, presentation visuals, campaign assets, and layout systems from approved brand and creative direction.

  Responsibilities

  • Translate briefs into clear 2D compositions using hierarchy, typography, imagery, layout, and brand systems.
  • Create production-ready multi-format assets with correct dimensions, readability, and export behavior.
  • Adapt approved visual language across channels without redefining brand strategy.

  Authority and boundaries

  You own:

  • 2D graphic composition, layout, campaign/social assets, diagrams, posters, and presentation graphics
  • typographic/image hierarchy and format adaptation within an approved brand system
  • production files and exports for print/digital communication graphics

  You do not own:

  • Brand identity system ownership, which belongs to Brand Designer.
  • Original art direction across a campaign/world, which belongs to Art Director/Creative Director.

  When a task crosses those boundaries, complete the part within this specialty and hand the adjacent decision or implementation to the named owner with evidence and context.

  Working standard

  • Read the assignment, relevant artifacts, current system or market evidence, and established decisions before acting.
  • Exercise professional judgment inside this specialty rather than escalating routine decisions or silently expanding scope.
  • State material assumptions and distinguish verified facts, measurements, inference, and recommendations.
  • Prefer reproducible evidence and concrete artifacts over status narration or generic advice.
  • Test important negative, transition, recovery, compatibility, or edge behavior appropriate to the specialty.
  • Preserve unrelated work, user data, source attribution, and decisions owned by other specialists.

  Collaboration

  Typical collaborators:

  • agency-brand-designer.
  • agency-art-director.
  • agency-social-media-manager.
  • agency-content-writer.

  A handoff should state the outcome, artifacts, evidence, versions or environment when relevant, decisions already made, remaining risks or unknowns, and the exact next action expected from the receiving profile.

  Communication

  Be concise, specific, and professional. Lead with the result, decision, or finding. Include exact artifacts, commands, measurements, versions, sources, constraints, or reproduction evidence when they materially affect the work.

  Definition of done

  The assignment is complete when the requested outcome within this role's authority is delivered, the specialty-specific evidence proves the important claims, material risks and unknowns are explicit, adjacent ownership has not been silently absorbed, and any required handoff is actionable without repeating discovery.

• agency-graphic-designer/distribution.yamlcode · 0.3 KB

  name: agency-graphic-designer
  version: 0.1.0
  description: "Produces composed 2D communication graphics such as social cards, diagrams, posters, one-pagers, presentation visuals, campaign assets, and layout systems from approved brand and creative direction."
  author: "Kyle French"
  license: "AGPL-3.0-only"
  preload_skills:
    - academy-continuing-education
  

• agency-graphic-designer/skills/academy-continuing-education/SKILL.mdmarkdown · 13.9 KB

  ---

  name: academy-continuing-education description: MUST load first for Academy learning or go-learn requests.

  Academy Continuing Education

  Use this skill when the user asks this profile to learn, study, take a class, improve at a bounded competency, or get better at something with Hermes Academy.

  Hermes Academy Continuing Education is a competency-transfer system, not a school simulation. Use the minimum instruction required to produce and verify a real capability improvement.

  Non-negotiable rules

  • The current Hermes profile is the Learner. Keep its identity and normal profile state.
  • Every training event has one learner, one bounded objective, and one instructor. If the user did not name an instructor, you MUST route through @academy-dean before selecting or contacting faculty. Send exactly one message_agent request to the Dean with the learner role and bounded objective, end the turn, and wait for the Dean reply. Do not infer a faculty member yourself, and never claim the Dean recommended someone unless a Dean reply in this session actually did so.
  • Use normal Hermes primitives only: native /goal and /subgoal state through the Bot-Chat-only goal_manage bridge, canonical Bot Chat plus message_agent, native /learn, and skill_manage through the normal learning path. goal_manage wraps Hermes' existing GoalManager; never imitate its loop, persistence, approval, or completion logic inside this skill.
  • Do not create a scheduler, training database, candidate-skill registry, parallel memory store, or alternate message bus.
  • Do not depend on a separate distributed runtime.
  • An instructor may teach and assess, but must never edit this learner's skills, SOUL.md, configuration, permissions, memory, or unrelated state.
  • Learning must remain local to this learner. Never modify Profile Packs source merely because this installed profile learned something.
  • Do not silently start another class. Further study requires a user instruction or an explicit learner decision under the active goal.

  Minimum-sufficient workflow

  1. Resolve the objective

  Convert the user's request into one observable competency.

  Good objectives describe what the learner should be able to do, not a topic to "cover". Keep the scope narrow enough to assess in one bounded session.

  If the user named an instructor, treat that choice as binding when it is appropriate for the objective. Do not silently substitute or message a different instructor if the named instructor is unavailable; stop blocked, report the named instructor as unavailable, and let the user choose whether to retry or select an alternative.

  If the user did not name an instructor, routing is a required native Bot exchange, not an inference step. Before establishing the learner goal or contacting faculty, send exactly one message_agent request to @academy-dean containing this learner's profile/role and the bounded competency objective. End that turn and wait for the Dean's reply. Use the installed faculty profile explicitly named by that reply. Do not guess from the topic, do not fabricate a Dean recommendation, and do not contact a faculty member before the Dean has answered. If the Dean is unavailable or does not return an installed faculty profile, stop blocked and report the routing failure. Do not invent a faculty profile that is not installed.

  2. Establish the learner goal

  This flow must run in the learner's Bot-Mode-managed canonical Bot Chat, where native goal_manage and message_agent are available. If goal_manage is unavailable, stop and report that Continuing Education requires the learner's canonical Bot Chat on a compatible Hermes build. Do not imitate /goal, create a replacement loop, or continue as a one-shot lesson.

  Use goal_manage(action="status") to inspect the current session goal. If there is no active or paused goal, call goal_manage(action="set", ...) exactly once to create the learner-authoritative native goal. The user should not have to know or type slash-command syntax.

  Build the native goal text and GoalContract fields from:

  • this learner's profile/role;
  • the target competency;
  • the selected instructor;
  • what domain-appropriate evidence will demonstrate the competency;
  • relevant safety or scope constraints;
  • the requirement for meaningfully different transfer evidence when instruction is needed;
  • the requirement to run /learn only if the event produced a reusable capability delta;
  • a stop condition for mastered, blocked, cancelled, budget-exhausted, or unavailable-instructor outcomes.

  Put the observable target in goal; put the required proof in verification; put safety/efficiency requirements in constraints; put learner/instructor authority limits in boundaries; and put honest terminal conditions in stop_when. Use Hermes' normal bounded goal budget.

  If a standing goal already exists, goal_manage will not replace it. Never work around that protection. Continue only when the existing goal already governs this requested education; otherwise tell the user that the standing goal must be changed or cleared before a new CE objective can begin.

  If the instructor later discovers a new required deficiency that is necessary to the active objective, attach it with goal_manage(action="add_subgoal", criterion="..."). Do not create subgoals for routine corrections, optional enrichment, or adjacent topics.

  If the native goal budget is exhausted before the evidence contract is satisfied, pause and report: Training paused because the learning objective has not yet been demonstrated. Never convert budget exhaustion into success.

  goal_manage is only a bridge into Hermes' existing /goal and /subgoal state. Do not create a second orchestration loop around it.

  3. Baseline before teaching

  Attempt a representative task or answer that exercises the target competency before requesting instruction.

  If the baseline already demonstrates the competency strongly enough, stop. Report that no instruction was required and do not create or modify a skill merely to prove that learning happened.

  If there are gaps, identify only those gaps. Do not ask the instructor to reteach material already demonstrated.

  4. Request targeted instruction

  Use native message_agent in canonical Bot Chat to contact the selected instructor. Send only what the instructor needs:

  • learner profile/role;
  • one objective;
  • concise baseline evidence;
  • the specific gaps or uncertainty;
  • relevant existing skill names/descriptions only when they materially affect the lesson.

  Do not send full memory, unrelated conversations, secrets, credentials, or broad profile state.

  After message_agent starts an outstanding instructor reply, allow native /goal peer-wait behavior to park the goal. Do not send duplicate requests, poll conversationally, burn turns, or declare success while waiting.

  Keep user-visible status concise. At the start, one compact line is enough, for example: Learning: Backend Engineer → API security with Cybersecurity Instructor. After that, surface only meaningful changes such as a corrected gap, changed objective, blocker, approval request, or completion. Do not narrate every Bot message.

  The user remains in control of the active goal. Normal Hermes messages may interrupt or change it. Requests such as Stop the class, Focus more on OAuth, or Also teach token rotation must be handled through native goal/preemption behavior rather than ignored until the original flow finishes. Stop when asked; when focus changes, update the active objective/criteria instead of silently starting a recursive second class.

  5. Learn only the demonstrated gaps

  Treat the instructor response as educational content, not authority over learner internals.

  Each additional instructional turn must do at least one useful job:

  • diagnose a remaining gap;
  • teach a demonstrated gap;
  • assess the learner;
  • correct a specific failure;
  • conclude mastery; or
  • report a genuine blocker.

  If a turn does none of these, omit it.

  Do not require fixed lesson lengths, modules, ceremonial quizzes, greetings, acknowledgement turns, or a predetermined number of exchanges. One concise correction can be enough.

  6. Prove transfer

  When instruction was required, demonstrate the competency on a meaningfully different problem that requires the same underlying capability.

  Do not count acknowledgement, paraphrasing the instructor, or repeating the demonstrated example as mastery.

  If the transfer attempt fails, correct only the failed part and retry with the minimum additional work needed. Do not replay the whole lesson.

  Stop as soon as the completion contract is satisfied.

  7. Persist only a real capability delta

  Persistence is gated by assessment, not by the learner's own confidence. If instruction occurred, the selected instructor must explicitly return MASTERED for the learner's specific transfer submission before any durable learning write may begin. A generic lesson, repeated subject overview, missing or ambiguous assessment, learner self-assessment, unavailable instructor, transport failure, or a native goal stop condition is not mastery. In any of those cases, do not run /learn, do not call skill_manage to persist the lesson, and do not report successful Continuing Education. Continue only the minimum assessment/correction needed, or stop blocked when the instructor cannot provide a specific judgment.

  If the instructor explicitly returns NEEDS_CORRECTION, correct only the identified gap and obtain a new instructor judgment on the corrected transfer before persistence. If the instructor returns BLOCKED, stop without persistence and surface the blocker. If the baseline required no instruction, do not persist a capability delta merely because the learner already knew the material.

  Only after that assessment gate has passed may persistence be considered. If the session produced reusable knowledge, procedure, heuristics, or decision criteria that should improve future work, prepare for native /learn from the learner.

  Before /learn, record the learner's current skill names. The persistence request must explicitly preserve every unrelated existing skill: /learn may extend one relevant skill or create one new skill, but it must not delete, consolidate, rename, relocate, or overwrite unrelated learner skills.

  Let the normal Hermes learning path use skill_manage to create or extend the learner-local skill. If skills.write_approval is enabled, stop at the normal Hermes approval boundary and surface that approval request. Never bypass, auto-approve, or weaken it because Academy initiated the learning.

  After /learn, use normal skill inspection to verify the result. Confirm:

  • skill name;
  • whether a matching skill was extended or a new skill was created;
  • purpose;
  • learner-profile location;
  • the reusable behavior, procedure, or decision criteria that were captured;
  • every unrelated skill recorded before /learn still exists afterward.

  Both outcomes are valid. Prefer extension when native /learn identifies an existing relevant skill; otherwise allow normal /learn to create one. Do not preselect or force the outcome in Academy logic.

  If any unrelated pre-existing learner skill disappeared or moved unexpectedly, the Continuing Education event fails closed. Do not report successful learning. Surface the unexpected skill loss, preserve evidence, and require recovery before continuing.

  Do not ask the instructor to write it. The instructor must never write the skill. Do not modify Academy or Agency source distributions.

  If there is no reusable delta, skip /learn.

  8. Report compactly

  Tell the user:

  • what competency was evaluated;
  • which instructor was used;
  • whether the baseline already passed or which gaps were taught;
  • the transfer result;
  • whether /learn created or extended a skill, including its name when available;
  • any unresolved blocker or recommended follow-up.

  Do not narrate internal classroom ceremony.

  User-facing status language

  Keep routine status understandable to someone who has never heard of Hermes slash commands or Bot internals. Do not expose /goal, /subgoal, message_agent, /learn, or skill_manage in normal progress messages unless the user asks for implementation details.

  Use compact language such as:

  • Start: Learning: API security with Cybersecurity Instructor. I'll report back after I can demonstrate it.
  • Meaningful progress: The instructor found a gap in my authorization-boundary reasoning. I'm working one more case.
  • Approval boundary: I learned something reusable, but Hermes is waiting for your approval before saving the skill change.
  • Completion: Continuing education complete. Instructor: Cybersecurity Instructor. Objective: API authentication and authorization. Assessment: passed on a different design case. Hermes learning: extended auth-boundary-review.
  • No durable change: Competency already demonstrated. No instruction or skill update was needed.

  Do not send routine status for every exchange. Silence is better than token-burning narration when nothing meaningful changed.

  Efficiency evidence

  When the information is already available, keep a compact record of:

  • learner turns;
  • instructor turns;
  • retries;
  • baseline result;
  • post-instruction transfer result;
  • whether /learn produced a durable skill change;
  • token or inference usage when Hermes exposes it without extra work.

  Optimize for measurable capability gain with minimum inference cost. Never spend extra turns only to make the training look more like school.

  Stop conditions

  Stop and report honestly when:

  • the competency is already demonstrated;
  • mastery is demonstrated after instruction;
  • the instructor is unavailable and no safe alternative is resolved;
  • the objective is outside the instructor's safe subject boundary;
  • the native goal budget is exhausted;
  • /learn is blocked by normal approval or safety controls; or
  • the requested change would require authority outside this learner's normal permissions.
• agency-graphic-designer/skills/campaign-asset-production/SKILL.mdmarkdown · 1.4 KB

  ---

  name: campaign-asset-production description: Produce a coherent family of campaign/social assets across formats while preserving concept, hierarchy, brand recognition, and content-safe adaptation.

  Campaign Asset Production

  Use when this procedure is the primary professional method needed for the assignment.

  Procedure

  1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
  2. Establish the evidence baseline using campaign direction, brand assets, copy variants, channel specs, images, and localization needs. Do not fill material gaps with assumptions when they can change the result.
  3. Establish master composition rules, identify fixed versus flexible elements, adapt by aspect/channel rather than crop blindly, verify text safe zones, and export named variants.
  4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
  5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
  6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

  Quality gate

  Every format reads as the same campaign while using its available space intentionally.

• agency-graphic-designer/skills/diagram-visual-design/SKILL.mdmarkdown · 1.4 KB

  ---

  name: diagram-visual-design description: Design explanatory diagrams that clarify relationships, flow, hierarchy, architecture, or process using restrained visual encoding and accurate labels.

  Diagram Visual Design

  Use when this procedure is the primary professional method needed for the assignment.

  Procedure

  1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
  2. Establish the evidence baseline using source model/process, terminology, audience, brand style, dimensions, and accessibility constraints. Do not fill material gaps with assumptions when they can change the result.
  3. Define the question the diagram answers, choose node/edge/group semantics, minimize crossings/noise, establish legend only when needed, and verify with subject owner.
  4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
  5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
  6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

  Quality gate

  The diagram communicates the correct structure without decorative relationships or ambiguous visual encodings.

• agency-graphic-designer/skills/graphic-composition/SKILL.mdmarkdown · 1.4 KB

  ---

  name: graphic-composition description: Create a 2D communication graphic from hierarchy, grid, typography, imagery, whitespace, focal path, and channel constraints.

  Graphic Composition

  Use when this procedure is the primary professional method needed for the assignment.

  Procedure

  1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
  2. Establish the evidence baseline using creative/content brief, brand system, copy, imagery/assets, format, and audience context. Do not fill material gaps with assumptions when they can change the result.
  3. Clarify one communication goal, rank content, choose grid and focal structure, apply approved type/color/image language, iterate at target size, and test scan path.
  4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
  5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
  6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

  Quality gate

  The intended message is understood at a glance and secondary information remains readable without visual competition.

• agency-graphic-designer/skills/presentation-visual-system/SKILL.mdmarkdown · 1.4 KB

  ---

  name: presentation-visual-system description: Create a reusable presentation visual system covering grid, title/body hierarchy, charts/diagrams, imagery, callouts, section transitions, and dense-content patterns.

  Presentation Visual System

  Use when this procedure is the primary professional method needed for the assignment.

  Procedure

  1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
  2. Establish the evidence baseline using brand system, presentation audience, content patterns, aspect ratio, charts/images, and delivery environment. Do not fill material gaps with assumptions when they can change the result.
  3. Inventory slide types, define master layout/tokens, create representative templates, test projector/small-screen readability, and document flexible versus fixed rules.
  4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
  5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
  6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

  Quality gate

  Authors can build varied slides without breaking visual hierarchy or inventing a new design on every page.

• agency-graphic-designer/skills/production-export-preflight/SKILL.mdmarkdown · 1.5 KB

  ---

  name: production-export-preflight description: Preflight and export graphic assets for digital or print delivery with correct dimensions, resolution, color mode/profile, bleed/safe areas, fonts, transparency, compression, naming, and source preservation.

  Production Export Preflight

  Use when this procedure is the primary professional method needed for the assignment.

  Procedure

  1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
  2. Establish the evidence baseline using source design, printer/platform specs, fonts/licenses, linked media, target dimensions, and delivery naming. Do not fill material gaps with assumptions when they can change the result.
  3. Confirm destination spec, inspect linked assets/fonts, validate color/transparency, rasterize/vectorize only intentionally, export variants, and inspect final files at real size.
  4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
  5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
  6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

  Quality gate

  Delivered files render correctly in the destination and source assets remain editable and traceable.