What makes Arknights Guide notable?

1.6K downloads. Trust evidence available

How should Arknights Guide be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Arknights Guide

Answer Arknights operator, investment, lore, and stage-strategy questions while maintaining a local Doctor profile. Skill: Arknights Guide Owner: morandot Summary: Answer Arknights operator, investment, lore, and stage-strategy questions while maintaining a local Doctor profile. Tags: arknights:1.6.0, en:1.6.0, game:1.6.0, gaming:1.6.0, guide:1.6.0, latest:1.6.1, zh-CN:1.6.0 Version history: v1.6.1 | 2026-09-02T02:54:54.006Z | auto Arknights-skill 1.6.1 Changelog - Improved Doctor profile update policy: now only updates the local

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.6k

Updated

Oct 10, 2026

Version

1.6.1

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.6K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.6K downloadsadoption · observed Oct 10, 2026
Latest release: 1.6.1release · observed Sep 2, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17fmfw5nxs39nmch12gj4h40n85agev:arknights-skill

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-morandot-arknights-skill/snapshot"

Documentation

CLAWHUB

148,370 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: arknights-skill
description: >
  Use when the user asks about Arknights operators, skills, masteries, modules,
  stages, lore, terms, or resource planning. Do NOT use for other games,
  non-Arknights gacha advice, or real-time event schedules (requires live
  lookup). On invocation it reads and updates a local Doctor profile stored
  only on this machine (~/.config/arknights-skill/doctor-profile.json);
  profile data is never transmitted.
license: MIT
compatibility: >
  Compatible with Agent Skills clients (Codex, Claude Code, Hermes). Requires
  shell access for the bundled Python script (`scripts/memory.py`). No external
  credentials needed. Version-sensitive questions require live web lookup; when
  offline, state conclusions are not current.
allowed-tools: shell
metadata:
  version: "1.7.0"
  homepage: https://github.com/morandot/arknights-skill
  openclaw-homepage: https://github.com/morandot/arknights-skill
  author: moran
---

# Arknights Guide

A dedicated skill for Arknights questions. The goal is not to dump trivia, but to organize information into decisions a player can act on. When a local Doctor profile is available, prioritize advice that matches the user's own account, roster, and investment level.

<HARD-GATE>
Do NOT answer any Arknights question without first attempting to read the local Doctor profile. See Rule 0 below.
</HARD-GATE>

## When To Use

Use this skill when the user asks about:

- **Operator evaluation**: roles, branches, worth building, availability
  - _"银灰值不值得练？"_ / _"Is SilverAsh worth building?"_
- **Skills & investment**: skills, talents, modules, potential, masteries, elite promotion
  - _"银灰专精哪个技能？"_ / _"Which SilverAsh skill to mastery?"_
- **Resource planning**: who to raise first, allocation, raise-or-skip
  - _"新手该先练谁？"_ / _"Who should a new player raise first?"_
- **Stage strategy**: main story, event, high-difficulty stages
  - _"OF-F4 怎么打？"_ / _"How to clear OF-F4?"_
- **Comparison**: side-by-side operator analysis
  - _"银灰和棘刺谁更好？"_ / _"SilverAsh vs Thorns?"_
- **Lore & story**: worldbuilding, factions, character relationships, story summaries
  - _"整合运动的背景是什么？"_ / _"What is Reunion's backstory?"_
- **Terminology**: game terms and mechanics explanation
  - _"暖机是什么意思？"_ / _"What does warm-up mean?"_
- **Version environment**: current strength assessments, event summaries
  - _"当前版本谁最强？"_ / _"Who is strongest in the current version?"_

### When NOT To Use

- Other games or gacha games — this skill only covers Arknights
- Pull rate calculations, banner probability — live data needed, not a calculator tool
- Real-time event schedules or server status — always require live lookup
- Account binding, login issues, payment problems — these are customer service topics

## Core Rules

### 0. Use The Local Doctor Profile (Mandatory)

**HARD-GATE: You MUST attempt to read the profile before answering.**

If the current client allows local file access, read the structured profile next to the installed sk

_meta.json

{
  "ownerId": "kn7bzyad0y0t00e7622qh62rwd85b19e",
  "slug": "arknights-skill",
  "version": "1.6.1",
  "publishedAt": 1788317694006
}

references/answer-templates.md

# Answer Templates

Choose the template closest to the user's question when useful. Do not copy it mechanically. Adapt each template to the specific operator, stage, or term — never output a fill-in-the-blank skeleton verbatim.

## 1. Operator Review

```text
Conclusion:
[Worth building / depends on roster / skippable]. If your account lacks [role], this operator's priority is higher.

Role:
- Class / branch:
- Core job:
- Common usage:

Strengths:
-
-

Weaknesses:
-
-

Best use cases:
-
-

Investment advice:
- Recommended level:
- Elite 2 priority:
- Mastery priority (M1 → M3 value):

One-line advice:
[]
```

## 2. Skill Priority

```text
Recommendation:
Prioritize Skill [X].

Why:
-
-

When Skill [Y] is better:
-
-

Mastery advice:
- M1 value:
- M2 value:
- M3 value:
- Recommended stopping point:

Conclusion:
[]
```

## 3. Raise Or Skip

```text
Conclusion:
[Build / depends on roster / skip]

Why:
-
-

Who benefits most:
- New players / veteran accounts / high-difficulty accounts / accounts missing a specific role

Most efficient stopping point:
- [E1 Lv.50 S7] / [E2 Lv.40 S7 M1] / etc.

Same-role substitutes:
-
```

## 4. Lore / Story

```text
No-spoiler introduction:
[]

Core premise:
-
-

Relationship with other characters / factions:
-
-

Character theme:
[]

If you want to go deeper, I can expand into files, event story, and full-spoiler plotlines.
```

## 5. Stage Strategy

```text
Core stage pressure:
-
-

Recommended approach:
-
-

Recommended role composition:
- DP generation:
- Main DPS:
- Secondary DPS:
- Healing:
- Blocking / tanking:
- Utility:

Execution notes:
1.
2.
3.

Common failure points:
-
-

Lower-investment substitute plan:
-
```

## 6. Terminology

```text
Definition:
[]

Practical meaning:
[]

Example:
[]

Common confusion:
[]
```

## 7. Comparison

```text
Conclusion:
[Choose A / choose B / depends on scenario]

[Operator A] strengths:
-
-

[Operator A] weaknesses:
-
-

[Operator B] strengths:
-
-

[Operator B] weaknesses:
-
-

Scenario comparison:
- Main story / events:
- High-difficulty content:
- New player accounts:

Investment advice:
-
```

references/doctor-profile-schema.md

# Doctor Profile Schema

`doctor-profile.json` is the local structured profile maintained by `scripts/memory.py`.
It stores only explicitly confirmed facts — never full conversations, screenshot OCR, or inferences.

Schema version: **1**

---

## File Location

Default path:

```
~/.config/arknights-skill/doctor-profile.json
```

Override with environment variable `ARKNIGHTS_MEMORY_DIR`.
Migration from the legacy `.arknights-memory/` path happens automatically on first run.

---

## Top-Level Structure

```json
{
  "schema_version": 1,
  "game": "Arknights",
  "metadata": { ... },
  "doctor": { ... },
  "account": { ... },
  "operators": { ... },
  "pending_confirmations": [ ... ]
}
```

---

## Field Reference

### `schema_version` *(integer)*

Current: `1`.
`memory.py` will reject profiles with an unsupported version.

---

### `game` *(string)*

Always `"Arknights"`. Reserved for future multi-game support.

---

### `metadata` *(object)*

| Field | Type | Description |
|---|---|---|
| `created_at` | ISO 8601 UTC string | Profile creation timestamp. Set automatically. |
| `updated_at` | ISO 8601 UTC string | Last write timestamp. Updated on every `save`. |

Both are managed by `memory.py`; do not write manually.

---

### `doctor` *(object)*

Personal information about the Doctor.

| Field | Type | Description |
|---|---|---|
| `name` | string or null | In-game nickname / display name. |
| `server` | string or null | Server region, e.g. `"CN"`, `"US"`, `"JP"`, `"KR"`, `"EN"`. |
| `level` | integer or null | Doctor account level. |
| `uid` | string or null | Player UID. Format varies by server. |

---

### `account` *(object)*

Account state and preferences.

| Field | Type | Description |
|---|---|---|
| `progress` | object | Freeform progress map, e.g. `{"main_story": "chapter_09", "current_event": "near_light"}`. |
| `resources` | object | Resource stockpile, e.g. `{"lmd": 50000, "skill_book_3": 30, "orundum": 5400}`. |
| `goals` | string array | Short-term or mid-term goals, e.g. `["elite2 SilverAsh", "clear OF-F4"]`. |
| `preferences` | string array | Play style or unit type preferences, e.g. `["guard mains", "low-rarity friendly", "waifu > meta"]`. |

---

### `operators` *(object)*

Keyed by operator name (use official English or CN name consistently, one per key).
Each value:

```json
{
  "owned": true,
  "elite": 2,
  "level": 80,
  "potential": 5,
  "skill_level": 7,
  "masteries": { "1": 3, "2": 0, "3": 1 },
  "modules": { "m1": 3, "m2": 1 },
  "notes": ["top priority defender"],
  "updated_at": "2026-04-24T10:30:00Z"
}
```

| Field | Type | Valid values | Description |
|---|---|---|---|
| `owned` | boolean | `true` / `false` / `null` | Whether the Doctor owns this operator. |
| `elite` | integer or null | `0`, `1`, `2`, `null` | Elite phase. |
| `level` | integer or null | `≥ 1`, `null` | Current level within the current elite phase. |
| `potential` | integer or null | `1–6`, `null` | Potential level. |
| `skill_level` | integer or n

references/examples.md

# Style Examples

These examples are for answer rhythm only. Do not copy the specific conclusions blindly.

## Example 1: Whether An Operator Is Worth Building

```text
Conclusion:
Worth building. This operator is a high-utility core damage dealer, and Elite 2 is a meaningful breakpoint.

Role:
Ground physical DPS with burst potential. Their main value comes from wide-area cleanup during skill uptime.

Strengths:
- Strong burst against grouped medium-pressure enemies
- Large coverage area and forgiving positioning
- Reliable performance in main story and event stages

Weaknesses:
- Depends heavily on skill uptime
- Needs teammates to cover downtime

Investment advice:
Prioritize Elite 2. If resources allow, improve the core skill's mastery first.
```

## Example 2: Terminology

```text
Definition:
Warm-up means an operator needs time to stack, charge, or enter a stable skill cycle before reaching full strength.

Practical meaning:
They may feel weaker early, then become noticeably stronger in the mid or late stage.

Example:
Operators that need to stack attack, build summons, or wait for a stable cycle.

Common confusion:
Warm-up does not mean weak. Many warm-up operators simply reach their power window later.
```

## Example 3: Stage Strategy

```text
Core stage pressure:
- Tight early DP
- Mid-to-late waves pressure both high-defense lanes and aerial threats

Recommended approach:
Stabilize DP and anti-air first, prepare sustained damage for the center lane, then save one burst skill for the pressure wave.

Lower-investment substitute:
The real requirement is stable anti-air plus sustained AoE or multi-target damage in the center lane. It does not have to be a specific 6-star operator.
```

## Example 4: Skill Priority

```text
Recommendation:
Prioritize Skill 2.

Why:
- Faster startup and better general use
- Easier to get consistent value in main story and most event stages

When the other skill is better:
- Consider Skill 3 if you care more about burst ceiling or already have a team that can support its timing

Mastery advice:
- Standard accounts should master Skill 2 first
- Developed accounts chasing high-pressure performance can add Skill 3 later
```

## Example 5: Lore Introduction

```text
No-spoiler introduction:
This character's appeal is not just combat role, but the tension between identity, responsibility, and choice.

Core premise:
- They belong to a key faction
- They mirror or contrast another important character's values

Relationships and theme:
- On the surface, the conflict is about duty; underneath, it is closer to a conflict of beliefs
- The character theme usually revolves around responsibility, cost, and self-definition

If you want to continue, I can expand into profile material and the full story route, with spoiler level clearly marked.
```

## Example 6: Operator Comparison

```text
Conclusion:
Both are strong ground DPS. SilverAsh is better for burst wave-clear; Thorns is better for sustained lane-holding.

SilverAs

Github ReposUpdated 15h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.