[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C68C77CCDVG8Y5X903T386":3,"skill-same:01M6C68C77CCDVG8Y5X903T386":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6C68C77CCDVG8Y5X903T386","clerk-android",null,"Implement Clerk authentication for native Android apps using Kotlin and Jetpack Compose with clerk-android source-guided patterns. Use for prebuilt AuthView\u002FUserButton or custom API-driven auth flows. Do not use for Expo or React Native projects.","Allternit\u002Fallternit-platform","Allternit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250397232?v=4","01M6C67T2SPVP033M7REAAHYHX","01M6C67T7CXM1DKVQY8DFAFRB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-android\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"clerk","clerk android","android","compose","clerk authentication","source","studio","Android Studio","flows","native","apps","jetpack","gradle","expo","jetpack compose","dependency","use","react native","webfetch","kotlin","projects","api","authentication","auth","react","implement","2026-11-10 10:12:30",false,"---\nname: clerk-android\ndescription: Implement Clerk authentication for native Android apps using Kotlin and\n  Jetpack Compose with clerk-android source-guided patterns. Use for prebuilt AuthView\u002FUserButton\n  or custom API-driven auth flows. Do not use for Expo or React Native projects.\nlicense: MIT\nallowed-tools: WebFetch\nmetadata:\n  author: clerk\n  version: 1.2.0\ncompatibility: Requires Android Studio and clerk-android Gradle dependency\n---\n\n# Clerk Android (Native)\n\nThis skill implements Clerk in native Android projects by following current `clerk-android` SDK and docs patterns.\n\n## Activation Rules\n\nActivate this skill when either condition is true:\n- The user explicitly asks for Android, Kotlin, Jetpack Compose, or native mobile Clerk implementation on Android.\n- The project appears to be native Android (for example `build.gradle(.kts)` with Android plugins, `AndroidManifest.xml`, `app\u002Fsrc\u002Fmain\u002Fjava`, Compose UI files).\n\nDo not activate this skill when either condition is true:\n- The project is Expo.\n- The project is React Native.\n\nIf Expo\u002FReact Native signals are present, route to the general setup skill instead.\n\n## What Do You Need?\n\n| Task | Reference |\n|------|-----------|\n| Prebuilt AuthView \u002F UserButton (fastest) | references\u002Fprebuilt.md |\n| Custom API-driven auth flows (full control) | references\u002Fcustom.md |\n\n## Quick Start\n\n| Step | Action |\n|------|--------|\n| 1 | Confirm project type is native Android and not Expo\u002FReact Native |\n| 2 | Determine flow type (`prebuilt` or `custom`) and load the matching reference file |\n| 3 | Ensure a real Clerk publishable key exists (or ask developer) |\n| 4 | Ensure correct Clerk artifacts are installed for the selected flow |\n| 5 | Read official Android quickstart and verify required setup (Native API, min SDK\u002FJava, manifest, initialization) |\n| 6 | Inspect `clerk-android` source\u002Fsample patterns relevant to selected flow |\n| 7 | Implement flow by following only the selected reference checklist |\n\n## Decision Tree\n\n```text\nUser asks for Clerk in Android\u002FKotlin\n    |\n    +-- Expo\u002FReact Native project detected?\n    |     |\n    |     +-- YES -> Do not use this skill\n    |     |\n    |     +-- NO -> Continue\n    |\n    +-- Existing auth UI detected?\n    |     |\n    |     +-- Prebuilt views detected -> Load references\u002Fprebuilt.md\n    |     |\n    |     +-- Custom flow detected -> Load references\u002Fcustom.md\n    |     |\n    |     +-- New implementation -> Ask developer prebuilt\u002Fcustom, then load matching reference\n    |\n    +-- Ensure publishable key and SDK initialization path\n    |\n    +-- Ensure correct Android artifacts are installed\n    |\n    +-- Verify quickstart prerequisites in project\n    |\n    +-- Implement using selected flow reference\n```\n\n## Flow References\n\nAfter flow type is known, load exactly one:\n- Prebuilt flow: [references\u002Fprebuilt.md](references\u002Fprebuilt.md)\n- Custom flow: [references\u002Fcustom.md](references\u002Fcustom.md)\n\nDo not blend the two references in a single implementation unless the developer explicitly asks for a hybrid approach.\n\n## Interaction Contract\n\nBefore any implementation edits, the agent must have both:\n- flow choice: `prebuilt` or `custom`\n- a real Clerk publishable key\n\nIf either value is missing from the user request\u002Fcontext:\n- ask the user for the missing value(s)\n- pause and wait for the answer\n- do not edit files or install dependencies yet\n\nOnly skip asking when the user has already explicitly provided the value in this conversation.\n\n## Source-Driven Templates\n\nDo not hardcode implementation examples in this skill. Inspect current `clerk-android` source\u002Fdocs for the installed SDK version before implementing.\n\n| Use Case | Source of Truth |\n|----------|-----------------|\n| SDK artifacts and dependency split (`clerk-android-api` vs `clerk-android-ui`) | `clerk-android` README and Android install docs |\n| SDK initialization and publishable key wiring | Android quickstart and `source\u002Fapi\u002F...\u002FClerk.kt` |\n| Prebuilt auth and profile behavior | `source\u002Fui\u002F...\u002FAuthView.kt`, `source\u002Fui\u002F...\u002FUserButton.kt`, and prebuilt sample |\n| Custom auth sequencing and factor handling | `source\u002Fui\u002Fauth\u002F*`, `source\u002Fapi\u002Fauth\u002F*`, and custom-flows sample |\n| Capability\u002Ffeature gating from instance settings | `Clerk` public fields (for example `enabledFirstFactorAttributes`, `socialProviders`, `isGoogleOneTapEnabled`, `mfaIsEnabled`) and environment model source |\n| Required Android setup checklist | Official Android quickstart (`\u002Fdocs\u002Fandroid\u002Fgetting-started\u002Fquickstart`) |\n\n## Execution Gates (Do Not Skip)\n\n1. No implementation edits before prerequisites\n- Do not edit project files until flow type is confirmed and a valid publishable key is available.\n\n2. Missing flow or key must trigger a question\n- If flow choice is missing, explicitly ask: prebuilt views or custom flow.\n- If publishable key is missing\u002Fplaceholder\u002Finvalid, explicitly ask for a real key.\n- Do not continue until both answers are provided.\n\n3. Publishable key wiring mode is mandatory\n- By default, wire the developer-provided key directly in `Clerk.initialize(...)`.\n- Do not introduce secret-management indirection unless explicitly requested.\n\n4. Artifact install policy is mandatory\n- Prebuilt flow: use `clerk-android-ui` (includes API).\n- Custom flow: use `clerk-android-api` unless prebuilt components are explicitly requested.\n- If Clerk artifacts are missing, add the latest stable release available.\n\n5. Android quickstart compliance is mandatory\n- Verify Native API is enabled for the Clerk app.\n- Verify Android requirements from quickstart are implemented in project (minimum SDK and Java target, manifest internet permission, app-level Clerk initialization).\n- Verify app waits for SDK initialization (`Clerk.isInitialized`) before assuming auth-ready state.\n\n6. Capability-driven behavior is mandatory\n- Use Clerk runtime capability\u002Fsettings state (for example enabled factors\u002Fsocial providers\u002FMFA flags) to gate flow behavior.\n- Do not hardcode factor assumptions that may conflict with dashboard configuration.\n\n7. Reference-file discipline is mandatory\n- Once flow is selected, follow only that flow reference file for implementation and verification.\n\n8. Custom-flow structure parity is mandatory\n- For `custom` flow, preserve multi-step auth progression and factor-specific handling (no single all-fields form by default).\n- Keep UI, state orchestration, and Clerk API integration in separate modules.\n\n9. Prebuilt preference is mandatory when selected\n- For `prebuilt` flow, do not rebuild auth forms with custom API calls unless explicitly requested.\n- Use `AuthView`\u002F`UserButton` as default building blocks.\n\n## Workflow\n\n1. Detect native Android vs Expo\u002FReact Native.\n2. If flow type is not explicitly provided, ask user for `prebuilt` or `custom`.\n3. If publishable key is not explicitly provided, ask user for it.\n4. Wait for both answers before changing files.\n5. Load matching flow reference file.\n6. Ensure `Clerk.initialize(...)` path and publishable key wiring are valid.\n7. Ensure dependencies\u002Fartifacts match selected flow.\n8. Review Android quickstart requirements and apply missing setup in project.\n9. Implement using selected reference checklist.\n10. Verify using selected reference checklist plus shared gates.\n\n## Common Pitfalls\n\n| Level | Issue | Prevention |\n|-------|-------|------------|\n| CRITICAL | Not asking for missing flow choice before implementation | Ask for `prebuilt` vs `custom` and wait before edits |\n| CRITICAL | Not asking for missing publishable key before implementation | Ask for key and wait before edits |\n| CRITICAL | Starting implementation before flow type is confirmed | Confirm flow first and load matching reference |\n| CRITICAL | Skipping Android quickstart prerequisites | Verify and apply required setup from official Android quickstart |\n| CRITICAL | Missing app-level `Clerk.initialize(...)` call | Initialize Clerk from `Application` startup path |\n| HIGH | Wrong artifact for chosen flow | Prebuilt: `clerk-android-ui`; custom: `clerk-android-api` |\n| HIGH | Rendering auth UI before SDK initialization completes | Gate UI with `Clerk.isInitialized` state |\n| HIGH | Hardcoding auth factors\u002Fsocial providers | Drive behavior from Clerk runtime capability fields |\n| HIGH | Using this skill for Expo\u002FReact Native | Detect and route away before implementation |\n\n## See Also\n\n- `clerk` skill for top-level Clerk routing\n- `clerk-setup` skill for cross-framework quickstart setup\n- `https:\u002F\u002Fgithub.com\u002Fclerk\u002Fclerk-android`\n- `https:\u002F\u002Fclerk.com\u002Fdocs\u002Fandroid\u002Fgetting-started\u002Fquickstart`\n","# Clerk Android (Native)\n\nThis skill implements Clerk in native Android projects by following current `clerk-android` SDK and docs patterns.\n\n## Activation Rules\n\nActivate this skill when either condition is true:\n- The user explicitly asks for Android, Kotlin, Jetpack Compose, or native mobile Clerk implementation on Android.\n- The project appears to be native Android (for example `build.gradle(.kts)` with Android plugins, `AndroidManifest.xml`, `app\u002Fsrc\u002Fmain\u002Fjava`, Compose UI files).\n\nDo not activate this skill when either condition is true:\n- The project is Expo.\n- The project is React Native.\n\nIf Expo\u002FReact Native signals are present, route to the general setup skill instead.\n\n## What Do You Need?\n\n| Task | Reference |\n|------|-----------|\n| Prebuilt AuthView \u002F UserButton (fastest) | references\u002Fprebuilt.md |\n| Custom API-driven auth flows (full control) | references\u002Fcustom.md |\n\n## Quick Start\n\n| Step | Action |\n|------|--------|\n| 1 | Confirm project type is native Android and not Expo\u002FReact Native |\n| 2 | Determine flow type (`prebuilt` or `custom`) and load the matching reference file |\n| 3 | Ensure a real Clerk publishable key exists (or ask developer) |\n| 4 | Ensure correct Clerk artifacts are installed for the selected flow |\n| 5 | Read official Android quickstart and verify required setup (Native API, min SDK\u002FJava, manifest, initialization) |\n| 6 | Inspect `clerk-android` source\u002Fsample patterns relevant to selected flow |\n| 7 | Implement flow by following only the selected reference checklist |\n\n## Decision Tree\n\n```text\nUser asks for Clerk in Android\u002FKotlin\n    |\n    +-- Expo\u002FReact Native project detected?\n    |     |\n    |     +-- YES -> Do not use this skill\n    |     |\n    |     +-- NO -> Continue\n    |\n    +-- Existing auth UI detected?\n    |     |\n    |     +-- Prebuilt views detected -> Load references\u002Fprebuilt.md\n    |     |\n    |     +-- Custom flow detected -> Load references\u002Fcustom.md\n    |     |\n    |     +-- New implementation -> Ask developer prebuilt\u002Fcustom, then load matching reference\n    |\n    +-- Ensure publishable key and SDK initialization path\n    |\n    +-- Ensure correct Android artifacts are installed\n    |\n    +-- Verify quickstart prerequisites in project\n    |\n    +-- Implement using selected flow reference\n```\n\n## Flow References\n\nAfter flow type is known, load exactly one:\n- Prebuilt flow: [references\u002Fprebuilt.md](references\u002Fprebuilt.md)\n- Custom flow: [references\u002Fcustom.md](references\u002Fcustom.md)\n\nDo not blend the two references in a single implementation unless the developer explicitly asks for a hybrid approach.\n\n## Interaction Contract\n\nBefore any implementation edits, the agent must have both:\n- flow choice: `prebuilt` or `custom`\n- a real Clerk publishable key\n\nIf either value is missing from the user request\u002Fcontext:\n- ask the user for the missing value(s)\n- pause and wait for the answer\n- do not edit files or install dependencies yet\n\nOnly skip asking when the user has already explicitly provided the value in this conversation.\n\n## Source-Driven Templates\n\nDo not hardcode implementation examples in this skill. Inspect current `clerk-android` source\u002Fdocs for the installed SDK version before implementing.\n\n| Use Case | Source of Truth |\n|----------|-----------------|\n| SDK artifacts and dependency split (`clerk-android-api` vs `clerk-android-ui`) | `clerk-android` README and Android install docs |\n| SDK initialization and publishable key wiring | Android quickstart and `source\u002Fapi\u002F...\u002FClerk.kt` |\n| Prebuilt auth and profile behavior | `source\u002Fui\u002F...\u002FAuthView.kt`, `source\u002Fui\u002F...\u002FUserButton.kt`, and prebuilt sample |\n| Custom auth sequencing and factor handling | `source\u002Fui\u002Fauth\u002F*`, `source\u002Fapi\u002Fauth\u002F*`, and custom-flows sample |\n| Capability\u002Ffeature gating from instance settings | `Clerk` public fields (for example `enabledFirstFactorAttributes`, `socialProviders`, `isGoogleOneTapEnabled`, `mfaIsEnabled`) and environment model source |\n| Required Android setup checklist | Official Android quickstart (`\u002Fdocs\u002Fandroid\u002Fgetting-started\u002Fquickstart`) |\n\n## Execution Gates (Do Not Skip)\n\n1. No implementation edits before prerequisites\n- Do not edit project files until flow type is confirmed and a valid publishable key is available.\n\n2. Missing flow or key must trigger a question\n- If flow choice is missing, explicitly ask: prebuilt views or custom flow.\n- If publishable key is missing\u002Fplaceholder\u002Finvalid, explicitly ask for a real key.\n- Do not continue until both answers are provided.\n\n3. Publishable key wiring mode is mandatory\n- By default, wire the developer-provided key directly in `Clerk.initialize(...)`.\n- Do not introduce secret-management indirection unless explicitly requested.\n\n4. Artifact install policy is mandatory\n- Prebuilt flow: use `clerk-android-ui` (includes API).\n- Custom flow: use `clerk-android-api` unless prebuilt components are explicitly requested.\n- If Clerk artifacts are missing, add the latest stable release available.\n\n5. Android quickstart compliance is mandatory\n- Verify Native API is enabled for the Clerk app.\n- Verify Android requirements from quickstart are implemented in project (minimum SDK and Java target, manifest internet permission, app-level Clerk initialization).\n- Verify app waits for SDK initialization (`Clerk.isInitialized`) before assuming auth-ready state.\n\n6. Capability-driven behavior is mandatory\n- Use Clerk runtime capability\u002Fsettings state (for example enabled factors\u002Fsocial providers\u002FMFA flags) to gate flow behavior.\n- Do not hardcode factor assumptions that may conflict with dashboard configuration.\n\n7. Reference-file discipline is mandatory\n- Once flow is selected, follow only that flow reference file for implementation and verification.\n\n8. Custom-flow structure parity is mandatory\n- For `custom` flow, preserve multi-step auth progression and factor-specific handling (no single all-fields form by default).\n- Keep UI, state orchestration, and Clerk API integration in separate modules.\n\n9. Prebuilt preference is mandatory when selected\n- For `prebuilt` flow, do not rebuild auth forms with custom API calls unless explicitly requested.\n- Use `AuthView`\u002F`UserButton` as default building blocks.\n\n## Workflow\n\n1. Detect native Android vs Expo\u002FReact Native.\n2. If flow type is not explicitly provided, ask user for `prebuilt` or `custom`.\n3. If publishable key is not explicitly provided, ask user for it.\n4. Wait for both answers before changing files.\n5. Load matching flow reference file.\n6. Ensure `Clerk.initialize(...)` path and publishable key wiring are valid.\n7. Ensure dependencies\u002Fartifacts match selected flow.\n8. Review Android quickstart requirements and apply missing setup in project.\n9. Implement using selected reference checklist.\n10. Verify using selected reference checklist plus shared gates.\n\n## Common Pitfalls\n\n| Level | Issue | Prevention |\n|-------|-------|------------|\n| CRITICAL | Not asking for missing flow choice before implementation | Ask for `prebuilt` vs `custom` and wait before edits |\n| CRITICAL | Not asking for missing publishable key before implementation | Ask for key and wait before edits |\n| CRITICAL | Starting implementation before flow type is confirmed | Confirm flow first and load matching reference |\n| CRITICAL | Skipping Android quickstart prerequisites | Verify and apply required setup from official Android quickstart |\n| CRITICAL | Missing app-level `Clerk.initialize(...)` call | Initialize Clerk from `Application` startup path |\n| HIGH | Wrong artifact for chosen flow | Prebuilt: `clerk-android-ui`; custom: `clerk-android-api` |\n| HIGH | Rendering auth UI before SDK initialization completes | Gate UI with `Clerk.isInitialized` state |\n| HIGH | Hardcoding auth factors\u002Fsocial providers | Drive behavior from Clerk runtime capability fields |\n| HIGH | Using this skill for Expo\u002FReact Native | Detect and route away before implementation |\n\n## See Also\n\n- `clerk` skill for top-level Clerk routing\n- `clerk-setup` skill for cross-framework quickstart setup\n- `https:\u002F\u002Fgithub.com\u002Fclerk\u002Fclerk-android`\n- `https:\u002F\u002Fclerk.com\u002Fdocs\u002Fandroid\u002Fgetting-started\u002Fquickstart`\n",{"name":5,"license":14,"metadata":49,"description":7,"allowed-tools":51,"compatibility":52},{"author":18,"version":50},"1.2.0","WebFetch","Requires Android Studio and clerk-android Gradle dependency","main","7db7c6f88fb96b6792195dacabdb088419b7a9fa",".agents\u002Fskills\u002Fclerk-android",0,"https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform","https:\u002F\u002Fgithub.com\u002FAllternit","https:\u002F\u002Fallternit.com","Allternit builds AI agents that work on your computer, in the cloud, and from your phone. Home of Allternit Desktop and Gizzi Code.","2026-11-12 03:40:39",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add Allternit\u002Fallternit-platform --skill clerk-android",{"tool":68,"command":69},"bunx","bunx skills add Allternit\u002Fallternit-platform --skill clerk-android",{"tool":71,"command":72},"pnpm","pnpm dlx skills add Allternit\u002Fallternit-platform --skill clerk-android","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-android\u002FSKILL.md",true,[76,82],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fcustom.md","REFERENCE","参考文档",3869,"https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-android\u002Freferences\u002Fcustom.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fprebuilt.md",2760,"https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclerk-android\u002Freferences\u002Fprebuilt.md",[87,114,133,156,180,210],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":44},"01M6C6GBWRCJNWQP5S16PKXB77","jev","Ask typed System One judgments (noul \u002F choice \u002F score) against Allternit's LOCAL System One server instead of prompting a chat model to \"return JSON\". Use when classifying, routing, scoring, or screening something and code needs a probability it can branch on, or when the user runs \u002Fjev. Official TypeSafe Jev is an optional, explicit remote lane.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002Ftools\u002Fsystem-one-local\u002Fskills\u002Fjev\u002FSKILL.md",[],[89,95,96,97,98,99,100,101,102,103,104,105,106,34,107,108,109,110,111,112,113],"official","routing","code","server","lane","system","json","model","choice","branch","ask","user","scoring","chat","local","probability","remote","can","when",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":44},"01M6C6G9CGB9MX47NSQ31QNNB7","jev-route","Route with local System One answers — map Choice + confidence to act \u002F confirm \u002F human lanes, or pick a model tier by Choice label. Also documents the separate `route-model` helper for OpenRouter's typesafe\u002Fjev-router (a chat-model router, NOT System One). Use for confidence routing, model-tier routing, or when the user runs \u002Fjev-route.","https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002Ftools\u002Fsystem-one-local\u002Fskills\u002Fjev-route\u002FSKILL.md",[],[89,121,122,123,96,100,102,124,103,125,106,34,126,127,108,128,109,129,130,131,132,113],"jev route","route","documents","pick","openrouter","router","model router","map","helper","with","for","model-tier",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":44},"01M6C6G6JZE0RC50QWWE6HG320","jev-guardrail","Screen text or agent tool calls with a battery of local System One Noul hazards plus a Score, with policy in code — and the Claude Code PreToolUse guard (hooks\u002Fpretooluse-guard) that puts deterministic hard rules first and lets Jev only raise friction. Use for injection\u002Fsecret\u002Fdestructive-action screening or when the user runs \u002Fjev-guardrail.","https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002Ftools\u002Fsystem-one-local\u002Fskills\u002Fjev-guardrail\u002FSKILL.md",[],[89,140,141,142,97,143,144,145,100,146,147,148,106,34,149,150,151,152,109,153,154,131,155,113],"jev guardrail","guardrail","policy","injection","first","guard","tool","text","Rules","friction","only","hooks","deterministic","battery","calls","agent tool",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":167,"publishedAt":44},"01M6C6G426P7Q5J3F98HVYDCB2","jev-fanout","Ask every independent System One question over the same state in ONE POST \u002Fv1\u002Fsystemone to the local server (speculative fan-out). Use for parallel judgments, compound commands, one-call turn assessment, or when the user runs \u002Fjev-fanout. Do not fire one HTTP call per question.","https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002Ftools\u002Fsystem-one-local\u002Fskills\u002Fjev-fanout\u002FSKILL.md",[162],{"categoryNo":163,"categoryName":164,"taxonomyType":165,"taxonomyTypeDesc":166},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[89,168,169,170,171,172,98,100,173,105,174,106,34,175,176,109,177,178,131,179,113],"fanout","jev fanout","http","assessment","state","parallel","question","do","call","post","v1","local server",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":44},"01M6C6G13D7JK869Q3DHMQ9542","memory-drive","Read and write the user's Allternit Memory Drive, a git repo of markdown memories in the open Agent Memory Repo format. Use at the start of a session to load what the user's agents remember (MEMORY.md), when the user says \"remember this\", when you learn a durable fact about the user or their work, and before answering questions that depend on past sessions.","https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002Ftools\u002Fmemory-drive-plugin\u002Fskills\u002Fmemory-drive\u002FSKILL.md",[],[187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,106,203,34,204,205,206,207,208,209,113],"memory","drive","memory drive","sessions","remember","learn","git","agent memory","start","open","markdown","format","work","repo","read","write","session","what the","memories","about","questions","you","load",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":219,"publishedAt":44},"01M6C6FX778N1047QAJ39Y582H","agent-orchestrator","Orchestrate external CLI agents (kimi, codex, agy, claude, grok, gizzi) through the Allternit Factory (gizzi agents \u002F orchestration \u002F workspace \u002F workflows). Use when the user asks to delegate, offload, or farm out implementation work to another CLI agent \u002F terminal session, or to run work outside this session to save tokens. Part of Allternit Agents \u002F Bot Agents — not a separate product.","https:\u002F\u002Fgithub.com\u002FAllternit\u002Fallternit-platform\u002Fblob\u002Fmain\u002Ftools\u002Fagent-orchestrator\u002FSKILL.md",[216],{"categoryNo":217,"categoryName":218,"taxonomyType":165,"taxonomyTypeDesc":166},"01JBSEEDCAT000000000000023","Skill与智能体开发",[220,221,222,223,224,225,226,227,228,229,230,231,232,199,233,234,203,34,235,236,237,238,239,240,241,242,113],"orchestrator","agent orchestrator","bot","cli","terminal","codex","orchestration","workflows","run","product","orchestrate","save","workspace","delegate","factory","grok","kimi","implementation","offload","tokens","cli agents","farm","terminal session"]