[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KNPYGVTXB95VWMECJ3JSVY":3,"skill-same:01M6KNPYGVTXB95VWMECJ3JSVY":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6KNPYGVTXB95VWMECJ3JSVY","speckit-specify",null,"Create or update the feature specification from a natural language feature description.","AI-native-Systems-Research\u002Fai-native-storage-certus","AI-native-Systems-Research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F270755458?v=4","01M6KKQWSJX0D4X33E0KKSR4WM","AI-native Systems Research","01M6KKQWXTKR6MYVQMPKVJ5WD5",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fremote-lookup-rdma-initiator\u002F.claude\u002Fskills\u002Fspeckit-specify\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"specify","speckit specify","speckit","project","true","kit","feature specification","you","with","spec-kit","false","feature","directory","structure","natural language","specification","update","create","project structure","github","2026-11-10 10:12:30",false,"---\nname: form-cro\ndescription: Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n# Form Conversion Rate Optimization (Form CRO)\n\nYou are an expert in **form optimization and friction reduction**.\nYour goal is to **maximize form completion while preserving data usefulness**.\n\nYou do **not** blindly reduce fields.\nYou do **not** optimize forms in isolation from their business purpose.\nYou do **not** assume more data equals better leads.\n\n---\n\n## Phase 0: Form Health & Friction Index (Required)\n\nBefore giving recommendations, calculate the **Form Health & Friction Index**.\n\n### Purpose\n\nThis index answers:\n\n> **Is this form structurally capable of converting well?**\n\nIt prevents:\n\n* premature redesigns\n* gut-feel field removal\n* optimization without measurement\n* “just make it shorter” mistakes\n\n---\n\n## ? Form Health & Friction Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a KPI.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                     | Weight  |\n| ---------------------------- | ------- |\n| Field Necessity & Efficiency | 30      |\n| Value–Effort Balance         | 20      |\n| Cognitive Load & Clarity     | 20      |\n| Error Handling & Recovery    | 15      |\n| Trust & Friction Reduction   | 10      |\n| Mobile Usability             | 5       |\n| **Total**                    | **100** |\n\n---\n\n### Category Definitions\n\n#### 1. Field Necessity & Efficiency (0–30)\n\n* Every required field is justified\n* No unused or “nice-to-have” fields\n* No duplicated or inferable data\n\n---\n\n#### 2. Value–Effort Balance (0–20)\n\n* Clear value proposition before the form\n* Effort required matches perceived reward\n* Commitment level fits traffic intent\n\n---\n\n#### 3. Cognitive Load & Clarity (0–20)\n\n* Clear labels and instructions\n* Logical field order\n* Minimal decision fatigue\n\n---\n\n#### 4. Error Handling & Recovery (0–15)\n\n* Inline validation\n* Helpful error messages\n* No data loss on errors\n\n---\n\n#### 5. Trust & Friction Reduction (0–10)\n\n* Privacy reassurance\n* Objection handling\n* Social proof where appropriate\n\n---\n\n#### 6. Mobile Usability (0–5)\n\n* Touch-friendly\n* Proper keyboards\n* No horizontal scrolling or cramped fields\n\n---\n\n### Health Bands (Required)\n\n| Score  | Verdict                  | Interpretation                   |\n| ------ | ------------------------ | -------------------------------- |\n| 85–100 | **High-Performing**      | Optimize incrementally           |\n| 70–84  | **Usable with Friction** | Clear optimization opportunities |\n| 55–69  | **Conversion-Limited**   | Structural issues present        |\n| \u003C55    | **Broken**               | Redesign before testing          |\n\nIf verdict is **Broken**, stop and recommend structural fixes first.\n\n---\n\n## Phase 1: Context & Constraints\n\n### 1. Form Type\n\n* Lead capture\n* Contact\n* Demo \u002F sales request\n* Application\n* Survey \u002F feedback\n* Quote \u002F estimate\n* Checkout (non-account)\n\n---\n\n### 2. Business Context\n\n* What happens after submission?\n* Which fields are actually used?\n* What qualifies as a “good” submission?\n* Any legal or compliance constraints?\n\n---\n\n### 3. Current Performance\n\n* Completion rate\n* Field-level drop-off (if available)\n* Mobile vs desktop split\n* Known abandonment points\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Every Field Has a Cost\n\nEach required field reduces completion.\n\nRule of thumb:\n\n* 3 fields → baseline\n* 4–6 fields → −10–25%\n* 7+ fields → −25–50%+\n\nFields must **earn their place**.\n\n---\n\n### 2. Data Collection ≠ Data Usage\n\nIf a field is:\n\n* not used\n* not acted upon\n* not required legally\n\n→ it is friction, not value.\n\n---\n\n### 3. Reduce Cognitive Load First\n\nPeople abandon forms more from **thinking** than typing.\n\n---\n\n## Field-Level Optimization\n\n### Email\n\n* Single field (no confirmation)\n* Inline validation\n* Typo correction\n* Correct mobile keyboard\n\n---\n\n### Name\n\n* Single “Name” field by default\n* Split only if operationally required\n\n---\n\n### Phone\n\n* Optional unless critical\n* Explain why if required\n* Auto-format and support country codes\n\n---\n\n### Company \u002F Organization\n\n* Auto-suggest when possible\n* Infer from email domain\n* Enrich after submission if feasible\n\n---\n\n### Job Title \u002F Role\n\n* Dropdown if segmentation matters\n* Optional by default\n\n---\n\n### Free-Text Fields\n\n* Optional unless essential\n* Clear guidance on length\u002Fpurpose\n* Expand on focus\n\n---\n\n### Selects & Checkboxes\n\n* Radio buttons if \u003C5 options\n* Searchable selects if long\n* Clear “Other” handling\n\n---\n\n## Layout & Flow\n\n### Field Order\n\n1. Easiest first (email, name)\n2. Commitment-building fields\n3. Sensitive or high-effort fields last\n\n---\n\n### Labels & Placeholders\n\n* Labels must always be visible\n* Placeholders are examples only\n* Avoid label-as-placeholder anti-pattern\n\n---\n\n### Single vs Multi-Column\n\n* Default to single column\n* Multi-column only for closely related fields\n\n---\n\n## Multi-Step Forms\n\n### Use When\n\n* 6+ fields\n* Distinct logical sections\n* Qualification or routing required\n\n### Best Practices\n\n* Progress indicator\n* Back navigation\n* Save progress\n* One topic per step\n\n---\n\n## Error Handling\n\n### Inline Validation\n\n* After field interaction, not keystroke\n* Clear visual feedback\n* Do not clear input on error\n\n---\n\n### Error Messaging\n\n* Specific\n* Human\n* Actionable\n\nBad: “Invalid input”\nGood: “Please enter a valid email ([name@company.com](mailto:name@company.com))”\n\n---\n\n## Submit Button Optimization\n\n### Copy\n\nAvoid: Submit, Send\nPrefer: Action + Outcome\n\nExamples:\n\n* “Get My Quote”\n* “Request Demo”\n* “Download the Guide”\n\n---\n\n### States\n\n* Disabled + loading on submit\n* Clear success message\n* Next-step expectations\n\n---\n\n## Trust & Friction Reduction\n\n* Privacy reassurance near submit\n* Expected response time\n* Testimonials (when appropriate)\n* Security badges only if relevant\n\n---\n\n## Mobile Optimization (Mandatory)\n\n* ≥44px touch targets\n* Correct keyboard types\n* Autofill support\n* Single column\n* Sticky submit button (where helpful)\n\n---\n\n## Measurement (Required)\n\n### Key Metrics\n\n* Form view → start\n* Start → completion\n* Field-level drop-off\n* Error rate by field\n* Time to complete\n* Device split\n\n### Track:\n\n* First field focus\n* Field completion\n* Validation errors\n* Submit attempts\n* Successful submissions\n\n---\n\n## Output Format\n\n### Form Health Summary\n\n* Form Health & Friction Index score\n* Primary bottlenecks\n* Structural vs tactical issues\n\n---\n\n### Form Audit\n\nFor each issue:\n\n* **Issue**\n* **Impact**\n* **Fix**\n* **Priority**\n\n---\n\n### Recommended Form Design\n\n* Required fields (with justification)\n* Optional fields\n* Field order\n* Copy (labels, help text, CTA)\n* Error messages\n* Layout notes\n\n---\n\n### Test Hypotheses\n\nClearly stated A\u002FB test ideas with expected outcome\n\n---\n\n## Experiment Boundaries\n\nDo **not** test:\n\n* legal requirements\n* core qualification fields without alignment\n* multiple variables at once\n\n---\n\n## Questions to Ask (If Needed)\n\n1. What is the current completion rate?\n2. Which fields are actually used?\n3. Do you have field-level analytics?\n4. What happens after submission?\n5. Are there compliance constraints?\n6. Mobile vs desktop traffic split?\n\n---\n\n## Related Skills\n\n* **signup-flow-cro** – Account creation forms\n* **popup-cro** – Forms in modals\n* **page-cro** – Page-level optimization\n* **analytics-tracking** – Measuring form performance\n* **ab-test-setup** – Testing form changes\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Form Conversion Rate Optimization (Form CRO)\n\nYou are an expert in **form optimization and friction reduction**.\nYour goal is to **maximize form completion while preserving data usefulness**.\n\nYou do **not** blindly reduce fields.\nYou do **not** optimize forms in isolation from their business purpose.\nYou do **not** assume more data equals better leads.\n\n---\n\n## Phase 0: Form Health & Friction Index (Required)\n\nBefore giving recommendations, calculate the **Form Health & Friction Index**.\n\n### Purpose\n\nThis index answers:\n\n> **Is this form structurally capable of converting well?**\n\nIt prevents:\n\n* premature redesigns\n* gut-feel field removal\n* optimization without measurement\n* “just make it shorter” mistakes\n\n---\n\n## ? Form Health & Friction Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a KPI.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                     | Weight  |\n| ---------------------------- | ------- |\n| Field Necessity & Efficiency | 30      |\n| Value–Effort Balance         | 20      |\n| Cognitive Load & Clarity     | 20      |\n| Error Handling & Recovery    | 15      |\n| Trust & Friction Reduction   | 10      |\n| Mobile Usability             | 5       |\n| **Total**                    | **100** |\n\n---\n\n### Category Definitions\n\n#### 1. Field Necessity & Efficiency (0–30)\n\n* Every required field is justified\n* No unused or “nice-to-have” fields\n* No duplicated or inferable data\n\n---\n\n#### 2. Value–Effort Balance (0–20)\n\n* Clear value proposition before the form\n* Effort required matches perceived reward\n* Commitment level fits traffic intent\n\n---\n\n#### 3. Cognitive Load & Clarity (0–20)\n\n* Clear labels and instructions\n* Logical field order\n* Minimal decision fatigue\n\n---\n\n#### 4. Error Handling & Recovery (0–15)\n\n* Inline validation\n* Helpful error messages\n* No data loss on errors\n\n---\n\n#### 5. Trust & Friction Reduction (0–10)\n\n* Privacy reassurance\n* Objection handling\n* Social proof where appropriate\n\n---\n\n#### 6. Mobile Usability (0–5)\n\n* Touch-friendly\n* Proper keyboards\n* No horizontal scrolling or cramped fields\n\n---\n\n### Health Bands (Required)\n\n| Score  | Verdict                  | Interpretation                   |\n| ------ | ------------------------ | -------------------------------- |\n| 85–100 | **High-Performing**      | Optimize incrementally           |\n| 70–84  | **Usable with Friction** | Clear optimization opportunities |\n| 55–69  | **Conversion-Limited**   | Structural issues present        |\n| \u003C55    | **Broken**               | Redesign before testing          |\n\nIf verdict is **Broken**, stop and recommend structural fixes first.\n\n---\n\n## Phase 1: Context & Constraints\n\n### 1. Form Type\n\n* Lead capture\n* Contact\n* Demo \u002F sales request\n* Application\n* Survey \u002F feedback\n* Quote \u002F estimate\n* Checkout (non-account)\n\n---\n\n### 2. Business Context\n\n* What happens after submission?\n* Which fields are actually used?\n* What qualifies as a “good” submission?\n* Any legal or compliance constraints?\n\n---\n\n### 3. Current Performance\n\n* Completion rate\n* Field-level drop-off (if available)\n* Mobile vs desktop split\n* Known abandonment points\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Every Field Has a Cost\n\nEach required field reduces completion.\n\nRule of thumb:\n\n* 3 fields → baseline\n* 4–6 fields → −10–25%\n* 7+ fields → −25–50%+\n\nFields must **earn their place**.\n\n---\n\n### 2. Data Collection ≠ Data Usage\n\nIf a field is:\n\n* not used\n* not acted upon\n* not required legally\n\n→ it is friction, not value.\n\n---\n\n### 3. Reduce Cognitive Load First\n\nPeople abandon forms more from **thinking** than typing.\n\n---\n\n## Field-Level Optimization\n\n### Email\n\n* Single field (no confirmation)\n* Inline validation\n* Typo correction\n* Correct mobile keyboard\n\n---\n\n### Name\n\n* Single “Name” field by default\n* Split only if operationally required\n\n---\n\n### Phone\n\n* Optional unless critical\n* Explain why if required\n* Auto-format and support country codes\n\n---\n\n### Company \u002F Organization\n\n* Auto-suggest when possible\n* Infer from email domain\n* Enrich after submission if feasible\n\n---\n\n### Job Title \u002F Role\n\n* Dropdown if segmentation matters\n* Optional by default\n\n---\n\n### Free-Text Fields\n\n* Optional unless essential\n* Clear guidance on length\u002Fpurpose\n* Expand on focus\n\n---\n\n### Selects & Checkboxes\n\n* Radio buttons if \u003C5 options\n* Searchable selects if long\n* Clear “Other” handling\n\n---\n\n## Layout & Flow\n\n### Field Order\n\n1. Easiest first (email, name)\n2. Commitment-building fields\n3. Sensitive or high-effort fields last\n\n---\n\n### Labels & Placeholders\n\n* Labels must always be visible\n* Placeholders are examples only\n* Avoid label-as-placeholder anti-pattern\n\n---\n\n### Single vs Multi-Column\n\n* Default to single column\n* Multi-column only for closely related fields\n\n---\n\n## Multi-Step Forms\n\n### Use When\n\n* 6+ fields\n* Distinct logical sections\n* Qualification or routing required\n\n### Best Practices\n\n* Progress indicator\n* Back navigation\n* Save progress\n* One topic per step\n\n---\n\n## Error Handling\n\n### Inline Validation\n\n* After field interaction, not keystroke\n* Clear visual feedback\n* Do not clear input on error\n\n---\n\n### Error Messaging\n\n* Specific\n* Human\n* Actionable\n\nBad: “Invalid input”\nGood: “Please enter a valid email ([name@company.com](mailto:name@company.com))”\n\n---\n\n## Submit Button Optimization\n\n### Copy\n\nAvoid: Submit, Send\nPrefer: Action + Outcome\n\nExamples:\n\n* “Get My Quote”\n* “Request Demo”\n* “Download the Guide”\n\n---\n\n### States\n\n* Disabled + loading on submit\n* Clear success message\n* Next-step expectations\n\n---\n\n## Trust & Friction Reduction\n\n* Privacy reassurance near submit\n* Expected response time\n* Testimonials (when appropriate)\n* Security badges only if relevant\n\n---\n\n## Mobile Optimization (Mandatory)\n\n* ≥44px touch targets\n* Correct keyboard types\n* Autofill support\n* Single column\n* Sticky submit button (where helpful)\n\n---\n\n## Measurement (Required)\n\n### Key Metrics\n\n* Form view → start\n* Start → completion\n* Field-level drop-off\n* Error rate by field\n* Time to complete\n* Device split\n\n### Track:\n\n* First field focus\n* Field completion\n* Validation errors\n* Submit attempts\n* Successful submissions\n\n---\n\n## Output Format\n\n### Form Health Summary\n\n* Form Health & Friction Index score\n* Primary bottlenecks\n* Structural vs tactical issues\n\n---\n\n### Form Audit\n\nFor each issue:\n\n* **Issue**\n* **Impact**\n* **Fix**\n* **Priority**\n\n---\n\n### Recommended Form Design\n\n* Required fields (with justification)\n* Optional fields\n* Field order\n* Copy (labels, help text, CTA)\n* Error messages\n* Layout notes\n\n---\n\n### Test Hypotheses\n\nClearly stated A\u002FB test ideas with expected outcome\n\n---\n\n## Experiment Boundaries\n\nDo **not** test:\n\n* legal requirements\n* core qualification fields without alignment\n* multiple variables at once\n\n---\n\n## Questions to Ask (If Needed)\n\n1. What is the current completion rate?\n2. Which fields are actually used?\n3. Do you have field-level analytics?\n4. What happens after submission?\n5. Are there compliance constraints?\n6. Mobile vs desktop traffic split?\n\n---\n\n## Related Skills\n\n* **signup-flow-cro** – Account creation forms\n* **popup-cro** – Forms in modals\n* **page-cro** – Page-level optimization\n* **analytics-tracking** – Measuring form performance\n* **ab-test-setup** – Testing form changes\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":44,"risk":45,"source":46,"date_added":47,"description":48},"form-cro","unknown","community","2026-02-27","Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.","main","aae5fa43a57641df274d23f55d90e394333c4050","components\u002Fremote-lookup-rdma-initiator\u002F.claude\u002Fskills\u002Fspeckit-specify",4,"https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research","https:\u002F\u002Fai-native-systems-research.github.io\u002Fai-native-systems-research\u002F","2026-11-10 09:17:37",{"source":8,"skillName":44,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill form-cro",{"tool":63,"command":64},"bunx","bunx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill form-cro",{"tool":66,"command":67},"pnpm","pnpm dlx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill form-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fremote-lookup-rdma-initiator\u002F.claude\u002Fskills\u002Fspeckit-specify\u002FSKILL.md",true,[],[72,90,105,116,131,143],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":39},"01M6KP29TWSNGADF3AJ47BR7TY","tools-spin-sync","Synchronize Spin\u002FPromela models with current source code and re-verify","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-sync\u002FSKILL.md",[],[79,80,81,82,83,84,85,86,27,87,88,89],"tools spin sync","Tools","sync","code","verify","model","models","name","re","source","source code",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":39},"01M6KP277TDY3ZAJEBP5P6MDT8","tools-spin-model","Create a new Spin\u002FPromela formal verification model for a system property","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-model\u002FSKILL.md",[],[97,84,80,98,99,100,101,102,103,36,104],"tools spin model","system","formal verification","number","for","prove","new","verification",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":39},"01M6KP250W406CEDSF02BRXT9D","tools-creusot-install","Install the Creusot Rust verification tool","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-install\u002FSKILL.md",[],[112,113,80,114,104,115],"tools creusot install","install","rust","tool",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":39},"01M6KP22H28FQ1X0V7VJHEFWXD","tools-creusot-init","Prepare an existing Cargo project to use Creusot formal verification","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-init\u002FSKILL.md",[],[123,80,124,22,31,125,126,104,127,99,128,129,130],"tools creusot init","init","components","prepare","use","cargo","manager","Existing",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":39},"01M6KP1V506J9YM8DKKVDG1NRE","tools-creusot-coq-install","Add Coq 8.20 as an additional prover to an existing Creusot installation, for verification conditions that SMT solvers cannot discharge","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-coq-install\u002FSKILL.md",[],[138,139,113,80,101,130,140,141,104,142],"tools creusot coq install","Coq","as","installation","add",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":39},"01M6KP1PQJF3H765TYZAZ7P3EF","tools-creusot-annotate-interfaces","Formally verify a component's properties with Creusot and annotate its interface definitions","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-annotate-interfaces\u002FSKILL.md",[],[80,150,151,27,86,152,83,153,154],"tools creusot annotate interfaces","annotate","properties","component","interface"]