How do I install the S Work skill?

Run npx skillmds add majiayu000/s-work in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is S Work safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with S Work?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is S Work free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published S Work?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

S Work by majiayu000 — Agent Skill

Name: S Work
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

S Work

General-purpose skill for Mechanic/Fen ecosystem work. Covers ecosystem context, development tools, component overview, and AFD principles. Use for everyday addon work, exploration, or when unsure which specialized skill to use. Triggers: work, build, develop, create, mechanic, fen, fencore, fenui, ecosystem, addon.

majiayu000 161bc4a 2 files · 2.9 KB Updated Sep 9, 2026 567 repo stars

File contents

Fen Ecosystem

Expert guidance for working in the Mechanic/Fen WoW addon development ecosystem.

The Reload Loop (MANDATORY)

After ANY addon code change, you MUST verify the changes in-game:

Ask the user to /reload in WoW (or trigger via keybinding CTRL+SHIFT+R)
Wait for the user to confirm the reload is complete
Then use the addon.output MCP tool (agent_mode=true) to get errors, tests, and console logs

CRITICAL: Do NOT call addon.output immediately after changes. The timing between reload and SavedVariables sync is unpredictable. Always wait for user confirmation before pulling output.

Ecosystem Components

Component	Purpose	Key Tools
Mechanic	Development hub	`env.status`, `addon.output`, `reload.trigger`
FenCore	Pure logic library	`fencore.catalog`, `fencore.search`, `fencore.info`
FenUI	UI widget library	`Layout`, `Panel`, `Tabs`, `Grid`, `Buttons`
MechanicLib	Bridge library	`RegisterAddon`, `Print`, `RegisterTest`

Essential MCP Tools

Task	MCP Tool
Get Addon Output	`addon.output` (agent_mode=true)
Lint Code	`addon.lint`
Run Tests	`addon.test`
Search APIs	`api.search`
Search FenCore	`fencore.search`
Env Status	`env.status`

AFD Core Principles

Mechanic follows Agent-First Development (AFD) — github.com/Falkicon/afd

Tool-First: All functionality must exist as an MCP tool before being added to any UI.
Structured Results: All tools return predictable JSON schemas with success, data, and error.
Agent Mode: Use agent_mode=true for distilled, AI-optimized output.

Routing Logic

Request type	Load reference
Component details, architecture	references/components.md
Daily workflows, patterns	references/workflow.md
Quick API reference	references/quick-api.md
MCP tool reference	../using-mechanic/references/afd-commands.md

---name: s-workdescription: General-purpose skill for Mechanic/Fen ecosystem work. Covers ecosystem context, development tools, component overview, and AFD principles. Use for everyday addon work, exploration, or when unsure which specialized skill to use. Triggers: work, build, develop, create, mechanic, fen, fencore, fenui, ecosystem, addon.--- # Fen Ecosystem Expert guidance for working in the Mechanic/Fen WoW addon development ecosystem. ## The Reload Loop (MANDATORY) After ANY addon code change, you MUST verify the changes in-game: 1. **Ask** the user to `/reload` in WoW (or trigger via keybinding CTRL+SHIFT+R) 2. **Wait** for the user to confirm the reload is complete 3. **Then** use the `addon.output` MCP tool (agent_mode=true) to get errors, tests, and console logs > **CRITICAL**: Do NOT call `addon.output` immediately after changes. The timing between reload and SavedVariables sync is unpredictable. Always wait for user confirmation before pulling output. ## Ecosystem Components | Component | Purpose | Key Tools | |-----------|---------|-----------| | **Mechanic** | Development hub | `env.status`, `addon.output`, `reload.trigger` | | **FenCore** | Pure logic library | `fencore.catalog`, `fencore.search`, `fencore.info` | | **FenUI** | UI widget library | `Layout`, `Panel`, `Tabs`, `Grid`, `Buttons` | | **MechanicLib** | Bridge library | `RegisterAddon`, `Print`, `RegisterTest` | ## Essential MCP Tools | Task | MCP Tool | |------|----------| | Get Addon Output | `addon.output` (agent_mode=true) | | Lint Code | `addon.lint` | | Run Tests | `addon.test` | | Search APIs | `api.search` | | Search FenCore | `fencore.search` | | Env Status | `env.status` | ## AFD Core Principles Mechanic follows **Agent-First Development (AFD)** — [github.com/Falkicon/afd](https://github.com/Falkicon/afd) 1. **Tool-First**: All functionality must exist as an MCP tool before being added to any UI. 2. **Structured Results**: All tools return predictable JSON schemas with `success`, `data`, and `error`. 3. **Agent Mode**: Use `agent_mode=true` for distilled, AI-optimized output. ## Routing Logic | Request type | Load reference | |--------------|----------------| | Component details, architecture | [references/components.md](references/components.md) | | Daily workflows, patterns | [references/workflow.md](references/workflow.md) | | Quick API reference | [references/quick-api.md](references/quick-api.md) | | MCP tool reference | [../using-mechanic/references/afd-commands.md](../using-mechanic/references/afd-commands.md) |

Frequently asked questions