Survivalcrafting

SKILLAI 工具
AI 工具 未标注权限 许可证不明确
安装这个技能

SurvivalCrafting专用技能,帮助AI Agent高效完成相关任务。

一句话选型结论

按资料字段整理

Survivalcrafting是AI 工具类的 Agent Skill,安装方式未标注,权限级别未标注,许可证不明确,有可直接复制的安装命令。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类AI 工具 安装方式未标注 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 未标注
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

未标注
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
skillhub install user_3c6cb52e/survival-crafting-d6w8
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    执行上面的命令安装;也可以把仓库里的 SKILL.md 手动放进客户端的 skills 目录。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

AI 工具
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方user_3c6cb52e仓库 未标注 · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式未标注安装包 community
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验未标注上游最后核验时间 · 数据更新 1791622471
正文体量7.5 KBSKILL.md 原文大小,越大说明说明书写得越细

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
组合多个 AI 能力

把写作、检索、总结串成一条流程。

搭工作流

把固定流程做成可重复调用的步骤。

做提示词与评测

整理提示词并对比输出效果。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有可直接复制的安装命令,不用自己翻文档找入口。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在AI 工具场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
Survivalcrafting当前 未标注权限 未标注 未标注 未标注 有
执行计划 只读 GitHub 仓库 151.5 万 Codex、Claude、Cursor 有
Playwright MCP 测试 浏览器控制 ClawHub 市场 136.5 万 OpenClaw 有
完成前的验证 未标注权限 GitHub 仓库 131.9 万 Codex、Claude、Cursor 有
子 Agent 驱动开发 只读 GitHub 仓库 131.2 万 Codex、Claude、Cursor 有
前端设计 执行命令 GitHub 仓库 125.6 万 Codex、Claude、Cursor 有

SKILL.md 全文

7.5 KB
模型实际读到的说明书原文,来自技能仓库

Survival Crafting

A playbook for survival-crafting games — the gather → craft → build loop, survival needs, the
crafting/tech progression, and base building. This is a compositional skill: it orchestrates
inventory data, world content, persistence, and threats. It does not re-teach those primitives;
it defines the loop and the pressure systems (needs, scarcity, escalation) that make survival
tense rather than tedious.

When to use

  • Use when the player gathers resources, crafts items/structures, manages survival needs, and
    builds a base
    against escalating threats: survival sandbox, crafting/base-building game.
  • Use when designing needs (hunger/thirst/temperature), a crafting tech tree, gathering loops,
    or base placement/building.

When not to use: crafting as a minor RPG feature → rpg. Permadeath grid dungeon →
roguelike. For inventory/items as data assets, use godot-resources /
unity-scriptableobjects; for world generation, procedural-gen.

Core loop

Gather raw resources → craft tools/items → build and upgrade a base → manage survival needs
→ explore farther for better resources → survive escalating threats → repeat at a higher tier.

Each loop should unlock the next loop (better tools → reach new biomes → new resources →
better crafts). When that ladder breaks, the game becomes a grind.

Must-have systems

  1. Resource nodes + gathering — harvestable world objects; tool requirements/tiers; respawn.
  2. Inventory — stacks, capacity (slots or weight), drop/transfer, hotbar.
  3. Crafting — recipes (inputs → output), a crafting station/tech gate, a tech tree.
  4. Survival needs — hunger, thirst, temperature, stamina, health, with decay + consequences.
  5. Base building — placeable structures, a build grid/snapping, storage, crafting stations.
  6. World + day/night — biomes/resources (often procedural); a time cycle driving threats.
  7. Threats — hostile creatures/weather/events that escalate; combat or avoidance.
  8. Save/load — world state, inventory, base, needs, progression; large-world persistence.

Design knobs

Knob Effect Notes
Needs decay rates pressure cadence Slow enough to explore, fast enough to matter.
Need-failure consequence stakes Damage over time, not instant death.
Resource scarcity / respawn exploration push Scarce near base → travel for more.
Tool tiers / gating progression ladder Better tool → new node types.
Recipe complexity / tech depth long-term goals Multi-step chains, not flat lists.
Inventory limit (slots/weight) logistics tension Forces base trips and storage.
Threat escalation curve difficulty over time Night/seasonal/event ramps.
Day length rhythm Day = gather, night = defend.

Patterns

1. Needs decay with graded consequences

# Pseudocode in the per-frame/per-tick update. dt = seconds. Needs fall; failure bleeds HP.
def update_needs(p, dt):
    p.hunger = max(0, p.hunger - HUNGER_RATE * dt)
    p.thirst = max(0, p.thirst - THIRST_RATE * dt)
    p.temp   = approach(p.temp, ambient_temperature(p), TEMP_RATE * dt)

    # Consequences are graded, not binary: warnings, then attrition — never instant death.
    if p.hunger == 0 or p.thirst == 0:
        p.hp -= STARVE_DAMAGE * dt          # damage over time creates urgency with recovery room
    if p.temp < COLD_THRESHOLD or p.temp > HEAT_THRESHOLD:
        p.hp -= EXPOSURE_DAMAGE * dt
    if p.hunger > 0 and p.thirst > 0 and not exposed(p):
        p.hp = min(p.max_hp, p.hp + REGEN_RATE * dt)   # safe + fed => heal

2. Crafting: validate, then atomically consume inputs

# Pseudocode. Recipes are data: inputs -> output, with an optional station/tech requirement.
recipe = {"id": "stone_axe",
          "inputs": {"wood": 3, "stone": 2}, "output": ("stone_axe", 1),
          "station": "workbench", "requires_tech": "basic_tools"}

def can_craft(recipe, inv, tech, station):
    if recipe.get("requires_tech") and recipe["requires_tech"] not in tech: return False
    if recipe.get("station") and recipe["station"] != station: return False
    return all(inv.count(item) >= n for item, n in recipe["inputs"].items())

def craft(recipe, inv, tech, station):
    if not can_craft(recipe, inv, tech, station): return False
    for item, n in recipe["inputs"].items(): inv.remove(item, n)   # consume all, then add
    inv.add(*recipe["output"])                                     # atomic: no partial craft
    return True

3. Gathering gated by tool tier

# Pseudocode. A node yields only if the held tool meets its required tier.
def harvest(node, tool):
    if tool.tier < node.required_tier:
        return notify("Need a better tool")        # e.g. stone node needs a pickaxe, not fists
    node.hp -= tool.power
    if node.hp <= 0:
        spawn_drops(node.drop_table)               # weighted drops (see roguelike loot pattern)
        node.start_respawn(node.respawn_time)      # node returns later; world isn't depleted forever

Pitfalls / failure modes

  • Needs that kill instantly → frustration and save-scumming. Make failure damage over time,
    with clear warnings and a recovery path (Pattern 1).
  • Grind without a ladder → gathering that never unlocks new gathering. Each tier must open
    the next (better tool → new node → new resource → better craft).
  • Non-atomic crafting → inputs consumed but output not granted on an edge case. Validate
    first, then consume-and-add as one step (Pattern 2).
  • Inventory with no limits → no logistics tension and no reason for a base/storage. Cap by
    slots or weight.
  • Permanently depleting the world → players strip the map and quit. Respawn nodes or
    regenerate resources over time.
  • Per-frame decay unscaled by dt → needs drain at different speeds on different hardware.
    Scale by dt.
  • No save / fragile save of a large world → a crash wipes hours. Persist world+base+needs
    incrementally; version it (see save-systems).
  • Flat threat curve → no late-game pressure. Escalate via night/season/event tiers.

Composition (build it from these skills)

  • Items/recipes as data: godot-resources / unity-scriptableobjects — items, recipes, tech tree, drop tables.
  • World: procedural-gen for biomes/resource placement; level-design for authored areas.
  • Persistence: save-systems for large-world state, base, inventory, needs, and versioning.
  • Threats: game-ai for creatures; the engine physics skill for melee/collision.
  • Building/placement: godot-tilemap / unity-tilemap-2d (2D) or godot-3d-essentials (3D) plus UI snapping.
  • UI: game-ui-ux for inventory/crafting/HUD layout and scaling; godot-ui-control for the concrete inventory, crafting menu, needs HUD, and build mode.

References

  • For the full needs model and thresholds, the crafting tech-tree graph, gather/respawn tuning,
    base-building grids, and threat escalation, read references/needs-and-crafting.md.

常见问题

5 问
答案由本站依据条目字段整理
Survivalcrafting怎么安装?

在支持 Skills 的客户端里执行:skillhub install user_3c6cb52e/survival-crafting-d6w8。安装方式为未标注。装完刷新技能列表或重开客户端。

Survivalcrafting支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

Survivalcrafting权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

Survivalcrafting收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

Survivalcrafting用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 未标注。