← Claude Code, start to finish
Claude Code

Plugins, Output Styles, and Scheduling in Claude Code

3 Aug 2026·6 min read

Days 7 and 8 went deep on MCP. Day 9 is Stage 5, Advanced: we package your setup as a plugin, change how Claude replies, and put it on a schedule.

Plugins: share your setup

A plugin is a folder with a manifest. It bundles skills, agents, hooks, and MCP servers, so your team installs one thing from a marketplace instead of copying files. Plugin skills are namespaced, like /my-plugin:hello.

claude --plugin-dir ./my-plugin
Point Claude Code at a local plugin folder while you build it.

Output styles: change the voice

Output styles change how Claude responds, not what it knows. They edit the system prompt. Four built-in styles ship: Default, Explanatory, Learning, and Proactive. Switch from /config, or set outputStyle in settings.

Scheduling: cloud, local, in-session

Routines run on the Anthropic cloud and keep working when your laptop is closed, on a schedule, an API call, or a GitHub event. The minimum interval is one hour. Desktop scheduled tasks run locally with file access, down to one minute. /loop repeats a prompt inside your open session for quick polling.

/loop 5m check if the deploy finished
A quick in-session loop to poll something while you work.
Status lineThe status line is a shell script at the bottom of the CLI. It reads session JSON on stdin and can show context usage, cost, and your git branch, always visible.

Try it: build a plugin from scratch

Enough theory. Let us build a tiny plugin from scratch, step by step, and run it. It is just a greeting skill named hello, and by the end you will call it as /my-plugin:hello.

  • Step 1: make the plugin folder and the manifest. Create my-plugin/.claude-plugin/plugin.json with a name, description, and version. That name becomes your skill namespace.
  • Step 2: add one skill under the plugin. Create my-plugin/skills/hello/SKILL.md. The folder name hello becomes the skill name, and its description tells Claude what it does.
  • Step 3: test it locally. Start Claude Code with --plugin-dir pointing at your folder, then run /my-plugin:hello inside the session.
  • Step 4: validate before you share. Run claude plugin validate to catch mistakes, then your teammates install it from a marketplace with /plugin install.
my-plugin/
├── .claude-plugin/
│   └── plugin.json
└── skills/
    └── hello/
        └── SKILL.md
The whole plugin: a manifest at the root, plus one skill folder.
{
  "name": "my-plugin",
  "description": "A greeting plugin to learn the basics",
  "version": "1.0.0"
}
The manifest at my-plugin/.claude-plugin/plugin.json. Only name is required; version is optional but recommended.
claude --plugin-dir ./my-plugin
/my-plugin:hello
Load the local plugin folder, then invoke the namespaced skill.

Here is what you will see. After --plugin-dir loads the plugin, /my-plugin:hello shows up in /help under the plugin namespace, and running it makes Claude greet you back. That is a working plugin, ready to share.

That is Stage 5. Next post: scaling — headless mode, git worktrees, and agent teams.

Plugins, Output Styles, and Scheduling in Claude Code · Ali Huzaifa