SkillsAdd

smithery/falkicon

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.

Installation

$ npx skills add smithery/falkicon --skill s-work
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

workers-best-practices Similar name
cloudflare/skills

Cloudflare Workers best practices for production applications. Use when writing, reviewing, or …

73K installs
expo-cicd-workflows Similar name
expo/skills 39.9K installs
firecrawl-workflows Similar name
firecrawl/firecrawl-workflows

Run outcome-focused Firecrawl workflows that produce deliverables such as research reports, lit…

31.4K installs
gws-workflow Similar name
googleworkspace/cli

Google Workflow: Cross-service productivity workflows.

30.2K installs
gws-workflow-email-to-task Similar name
googleworkspace/cli

Google Workflow: Convert a Gmail message into a Google Tasks entry.

29.4K installs
gws-workflow-meeting-prep Similar name
googleworkspace/cli

Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.

28.7K installs

Also in this package

Other skills from smithery/falkicon · top by installs.

npx skills add smithery/falkicon
s-test 0 s-research 0 s-release 0 s-lint 0 s-develop 0 s-debug 0 s-clean 0 s-audit 0 noisett 0 k-mechanic 0

Browse all from smithery/falkicon

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,581 B
  • docs SUMMARY.md 331 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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

  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)