Create a skill to author HIPs

Signed-off-by: George Jenkins <gvjenkins@gmail.com>

Author: gjenkins8

skills/hip-author-workspace/evals/evals.json

@@ -0,0 +1,26 @@
+{
+  "skill_name": "hip-author",
+  "evals": [
+    {
+      "id": 0,
+      "name": "feature-hip",
+      "prompt": "I want to write a HIP for adding native support for chart signing using Sigstore/cosign instead of the current PGP-based provenance system. The current .prov file approach is clunky and almost nobody uses it because PGP key management is painful. Cosign is already the standard in the container ecosystem and it would make chart verification way more accessible.",
+      "expected_output": "A well-structured HIP document with all required sections, proper YAML preamble with hip: 9999, type: feature, status: draft. Should address backwards compatibility with existing .prov files.",
+      "files": []
+    },
+    {
+      "id": 1,
+      "name": "process-hip",
+      "prompt": "I think we should create a formal process for how Helm handles security embargoes and coordinated disclosure with downstream distributors. Right now the SECURITY.md covers reporting but there's no documented process for how we coordinate with distro maintainers who package Helm before a CVE goes public.",
+      "expected_output": "A well-structured HIP document with type: process, addressing the coordination gap in security disclosure. Should reference existing SECURITY.md and governance docs.",
+      "files": []
+    },
+    {
+      "id": 2,
+      "name": "vague-idea",
+      "prompt": "I have a half-baked idea - what if Helm charts could somehow declare their resource requirements or dependencies on cluster capabilities? Like, a chart could say 'I need an ingress controller' or 'I need at least 3 nodes' and helm install would check that before deploying. I'm not sure if this is even feasible or if it's too broad.",
+      "expected_output": "Should help refine the vague idea into something concrete before producing any HIP text. Should probe scope, suggest narrowing, and only proceed to drafting after the idea is focused.",
+      "files": []
+    }
+  ]
+}

skills/hip-author-workspace/iteration-1/feature-hip/eval_metadata.json

@@ -0,0 +1,47 @@
+{
+  "eval_id": 0,
+  "eval_name": "feature-hip",
+  "prompt": "I want to write a HIP for adding native support for chart signing using Sigstore/cosign instead of the current PGP-based provenance system. The current .prov file approach is clunky and almost nobody uses it because PGP key management is painful. Cosign is already the standard in the container ecosystem and it would make chart verification way more accessible.",
+  "assertions": [
+    {
+      "name": "valid_yaml_preamble",
+      "description": "HIP starts with valid YAML frontmatter containing all required fields (hip, title, authors, created, type, status)",
+      "type": "structural"
+    },
+    {
+      "name": "placeholder_hip_number",
+      "description": "Uses hip: 9999 (or quoted '9999') as placeholder, not an invented number",
+      "type": "structural"
+    },
+    {
+      "name": "type_is_feature",
+      "description": "type field is set to 'feature'",
+      "type": "structural"
+    },
+    {
+      "name": "status_is_draft",
+      "description": "status field is set to 'draft'",
+      "type": "structural"
+    },
+    {
+      "name": "all_required_sections",
+      "description": "Contains all required sections: Abstract, Motivation, Rationale, Specification, Backwards compatibility, Security implications, How to teach this, Reference implementation, Rejected ideas, Open issues, References",
+      "type": "structural"
+    },
+    {
+      "name": "abstract_concise",
+      "description": "Abstract is roughly 100-300 words (not a full page, not a single sentence)",
+      "type": "quality"
+    },
+    {
+      "name": "backwards_compat_addresses_prov",
+      "description": "Backwards compatibility section explicitly addresses migration from existing .prov/PGP system",
+      "type": "content"
+    },
+    {
+      "name": "specification_has_details",
+      "description": "Specification section contains concrete technical details (CLI flags, file formats, or workflow descriptions), not just hand-waving",
+      "type": "content"
+    }
+  ]
+}

skills/hip-author-workspace/iteration-1/feature-hip/with_skill/grading.json

@@ -0,0 +1,46 @@
+{
+  "eval_name": "feature-hip",
+  "variant": "with_skill",
+  "expectations": [
+    {
+      "text": "valid_yaml_preamble",
+      "passed": true,
+      "evidence": "Found valid YAML frontmatter"
+    },
+    {
+      "text": "placeholder_hip_number",
+      "passed": true,
+      "evidence": "Found hip: 9999 placeholder"
+    },
+    {
+      "text": "status_is_draft",
+      "passed": true,
+      "evidence": "status is draft"
+    },
+    {
+      "text": "all_required_sections",
+      "passed": true,
+      "evidence": "All 11 required sections present"
+    },
+    {
+      "text": "abstract_concise",
+      "passed": true,
+      "evidence": "Abstract is 145 words (target: 100-300)"
+    },
+    {
+      "text": "type_is_feature",
+      "passed": true,
+      "evidence": "type is feature"
+    },
+    {
+      "text": "backwards_compat_addresses_prov",
+      "passed": true,
+      "evidence": "Backwards compat section references .prov/PGP"
+    },
+    {
+      "text": "specification_has_details",
+      "passed": true,
+      "evidence": "Specification is 733 words, has code examples"
+    }
+  ]
+}