Short answer
Skills do not come from one flat list. Current coverage shows combat progression, weapon-related skills and multiple learning paths, while the official experience description confirms persistent skill levels for each Cursed Fruit. Exact Skill Scroll drops, full mastery thresholds, all trainer inventories and Fruit-tree nodes are UNVERIFIED / HOLD.
Skill-system status matrix
| Question | Status | Practical use |
|---|---|---|
| Does the game include combat skills and progression? | SOURCE-BACKED CURRENT | Build your hotbar around skills you actually use on quests. |
| Can a weapon requirement matter for a skill? | SOURCE-BACKED CURRENT | Check the live weapon / skill description before changing equipment. |
| Do Fruit skill levels persist per Fruit after swapping? | OFFICIAL | A usable Fruit can be tested without assuming progress is lost. |
| Exact Scroll source, chance or boss drop | UNVERIFIED / HOLD | Do not farm a named enemy from an unverified table. |
| Exact skill costs, cooldowns, damage or mastery breakpoint | UNVERIFIED / HOLD | Read the live client and current patch notes. |
| Full Fruit skill tree for any Fruit | UNVERIFIED / HOLD | Do not copy node maps from an old build. |
A safe mastery loop
- Pick a small set of skills you want for the next quest band.
- Put those skills into normal combat rotations instead of saving every use for a boss.
- When the live UI offers an upgrade, read its exact wording and choose the bottleneck it fixes.
- Recheck after patches before committing resources around a remembered node path.
Skill Scroll checklist
Before treating a Scroll or NPC-skill lead as valuable, confirm:
| Check | Why it matters |
|---|---|
| Exact name in the live client | Avoids collisions with older names or another experience. |
| Weapon / style requirement | A skill can be unusable with your current setup. |
| Slot and rotation cost | A new button can displace a skill that actually carries your route. |
| Current source date | Early Access drop and trainer info can change quickly. |
Fruit skill tree release gate
A public tree needs a Fruit name, full current node order, prerequisite, cost, live effect, patch context and at least one independent verification route. Until then, the Fruit Database gives the official persistence fact and clearly marks per-Fruit trees as held.
Next step
If a skill decision depends on your Fruit and current Race / Trait description, use the Build Planner. It identifies the data you need from the live UI without inventing cross-system values.