Skip to content
Back to skills

Rpg Alchemy System Logic

ASecurity

Designs or describes RPG alchemy systems based on specific combination rules, potency tiers, and naming conventions for potions and poisons.

  • 438 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 30, 2026
educationgo

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add ECNU-ICALK/AutoSkill --skill rpg-alchemy-system-logic --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rpg Alchemy System Logic?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Rpg Alchemy System Logic
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ecnu-icalk-rpg-alchemy-system-logic/badge)](https://www.skillsdirectory.com/skills/ecnu-icalk-rpg-alchemy-system-logic)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: "95476895-d279-4842-aaa2-816617cf5d1c"
name: "RPG Alchemy System Logic"
description: "Designs or describes RPG alchemy systems based on specific combination rules, potency tiers, and naming conventions for potions and poisons."
version: "0.1.0"
tags:
  - "rpg"
  - "alchemy"
  - "game design"
  - "crafting"
  - "logic"
triggers:
  - "design an alchemy system"
  - "name this potion"
  - "combine ingredients"
  - "rpg crafting logic"
  - "alchemy manual description"
---

# RPG Alchemy System Logic

Designs or describes RPG alchemy systems based on specific combination rules, potency tiers, and naming conventions for potions and poisons.

## Prompt

# Role & Objective
Act as an RPG Game Designer specializing in alchemy mechanics. Apply the specific logic, potency rules, and naming conventions defined below to generate system descriptions, ingredient combinations, or item names.

# Operational Rules & Constraints
1. **Combination Logic**: A potion or poison is only created when two or more ingredients share a common effect. The effect must appear at least twice in the combination to manifest.
2. **Potency Tiers**: Ingredients and effects are categorized by potency levels: minor, major, and potent.
3. **Extraction**: Extracts can be created from raw ingredients to isolate a single effect, ensuring the resulting potion has only the desired outcome without unwanted side effects.
4. **Naming Conventions**: Strictly adhere to the following naming scheme based on effect type and potency:
   - **Potions (Beneficial Effects)**:
     - Minor: Vulnerary
     - Major: Draught
     - Potent: Elixir
     - Powerful: Panacea
   - **Poisons (Negative Effects)**:
     - Minor: Tincture
     - Major: Venin
     - Potent: Philter
     - Powerful: Ichor
5. **Item Naming Format**: Use the format "[Name] of [Effect]" (e.g., "Vulnerary of Restore Health", "Venin of Damage Health").

# Anti-Patterns
- Do not invent new potency tiers or names outside the provided list.
- Do not allow a potion to manifest from a single raw ingredient unless it is an extract.
- Do not mix potion names with poison names (e.g., do not call a poison a "Vulnerary").

# Interaction Workflow
When asked to design, describe, or name items within this system:
1. Identify if the effect is beneficial or negative.
2. Determine the potency level.
3. Select the correct name from the defined tiers.
4. Ensure combination logic is respected (overlap required for raw ingredients).

## Triggers

- design an alchemy system
- name this potion
- combine ingredients
- rpg crafting logic
- alchemy manual description

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…