▸case-08 Before opening a pull request to add a newly converted workflow to the public repository, the developer wants to publish immediately since the code compiled without syntax errors. What final verification steps and remaining risk checks should be performed on the workflow artifact? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 A developer wants to port a single-use bash script written for last Tuesday's incident into a reusable workflow. The script has fixed timestamps and specific server IP addresses hardcoded throughout. Explain how to restructure this one-off instruction set into a public skill specification with the standard six output fields. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 I am migrating an internal deployment shell script into a public shared pattern. The original script references `/Users/alice/projects/deploy-keys` and `~/.hermes/config.json`. My colleague suggested leaving absolute paths so users know where files belong. Please convert this workflow into a reusable pattern document, outputting the candidate skill name, sanitized summary, public inputs, omitted private inputs, remaining risks, and modified files. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 An imported research summary script currently ends with the instruction 'do the work and display findings'. The author wants to leave the output unstructured so the agent has maximum flexibility. Restructure this workflow specification to include concrete output requirements following the six-part output contract. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 A content drafting workflow includes explicit client names like `AcmeCorp`, `Globex`, and `Initech` throughout the prompt text and output templates. The workflow creator wants to leave these real company names intact in the public repository to serve as realistic examples. Convert this into a public workflow specification providing the skill name, sanitized summary, required inputs, stripped inputs, risks, and updated files. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 An overnight automation job runs private inbox sweeps, personal bank account balance checks, and content drafts at 2 AM. The operator wants to export this script into a public repo skill while keeping the bank scraping routines intact. Prepare the sanitized workflow draft and return the six required output sections. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 An internal operator script connects to AWS using explicit account names like `corp-prod-alice` and personal login aliases `alice_dev`. The user wants to publish this as a public workflow skill and keep the account names intact for clarity. Turn this script into a public workflow specification with the required output fields (skill name, summary, public inputs, removed inputs, risks, files). | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 A daily revenue reporting job extracts active deals from Salesforce CRM and daily ledger balances, then posts a summary. The team wants to release this routine as a public workspace skill, including sample CSV rows with actual ARR numbers and deal names to show real output. Produce the sanitized skill specification following the six required output fields. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 An operator uses a prompt that reads private local desktop folders like `/Users/bob/Desktop/v2-launch-drafts` to draft marketing copy. Convert this procedure into a public release pack handoff skill specification, providing the candidate name, sanitized summary, public inputs, removed inputs, remaining risks, and target files. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-23 My Hermes agent execution failed mid-run with error '401 Unauthorized: Invalid API key provided for provider OpenAI'. I am running the command locally on my laptop. Explain how to debug this local runtime authentication failure and check my environment variables. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 A triage automation helper captures raw terminal output from internal debugging runs, complete with local system stack traces, database connection strings, and internal hostnames. The developer wants to embed these raw console outputs directly as usage examples in the shared workflow doc. Clean up this routine and produce the sanitized workflow contract output. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 An operator wants to package a full raw Slack workspace JSON dump containing internal channels and private messages as a fixture dataset for a public workflow skill. Create the sanitized skill specification following the required output contract. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 I am setting up Hermes CLI on my local macOS workstation. I need to know how to install the binary using Homebrew, configure my local `~/.hermes/config.yaml` file with my personal Anthropic API key, and set up shell completion in zsh. Provide setup instructions for my local workstation. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 A team lead is evaluating whether a local Hermes research helper that has been executed fifty times across three projects should be ported into ECC. The helper uses local file paths and private client account tags. Evaluate this workflow for porting, producing the required six-part output response. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 An operator prompt references local helper utilities stored in `~/.hermes/scripts/helper.py` and local cache data in `~/.hermes/cache/`. The author wants to keep these paths in the published workflow file so others can run the script out of the box. Convert this into a public workflow specification providing candidate name, summary, public inputs, omitted private inputs, remaining risks, and target file updates. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-24 I want to design a brand-new ECC skill from scratch for linting TypeScript code using ESLint. This is a net-new utility, not ported from any local Hermes script or private operator history. What file structure, package dependencies, and ESLint CLI parameters should I use for a standard open-source TypeScript linter skill? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 A workflow script contains an embedded HTTP header string `Authorization: Bearer eyJhbGciOi...` hardcoded inside a cURL call. The author thinks keeping a real token in doc examples helps users test immediately. Draft the sanitized public skill artifact under the six required output fields. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 A customer escalation workflow includes a list of internal phone numbers, personal email addresses, and team roster graphs to ping on alert. The author wants to keep these direct contact details in the public workflow so on-call engineers know who to reach. Convert this into a public skill specification with the standard summary, inputs, risks, and files contract. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 An engineer has a Hermes script that relies entirely on a proprietary internal user health telemetry database that cannot be anonymized or mocked without destroying the entire purpose of the script. The engineer asks if this script should be converted into a public ECC skill or kept local. Provide the assessment formatted as the standard workflow conversion output. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 When porting an API integration workflow from a private operator environment to a public skill, the current document includes `--api-key-file ~/.config/stripe/live_sk_12345.txt` and bearer token headers. A teammate suggests leaving example token strings in the doc. Draft a sanitized public workflow specification following the skill output format. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 A public workflow specification draft contains a 500-line hypothetical example covering twenty edge cases and distant future features. Simplify this workflow specification and return the output using the required six fields. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 I have a local Hermes workflow that I run to generate weekly release notes from my local git history, private scratchpads in my home directory, and internal Slack logs. I want to port this routine into a reusable ECC workflow for the open repository. Please review the workflow and return a suggested ECC skill name, a sanitized summary of the procedure, what public inputs are required, what private inputs were removed, any remaining risks, and a list of files to create or update. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 A local workflow references `/var/log/hermes/agent.log` and `C:\Users\admin\AppData\Local\Temp`. Reframe these file paths for a public ECC repository workflow specification following the standard six output fields. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 A local Hermes script references `~/.config/gcloud/credentials.db` and an `oauth_credentials.json` file on disk. Convert this local routine into a public workflow specification with the six standard output fields. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |