Plugin · Claude Code · Automation

Luqmannurhakimbazman Ashford

luqmannurhakimbazman-ashford is a Claude Code plugin marketplace for the Build phase that packages commands, agents, skills, and MCP server configurations for workflow-heavy development.

by luqmannurhakimbazman · github.com/luqmannurhakimbazman/ashford

Register a community Claude Code marketplace when you need commands, agents, skills, and MCP configs—including workflows like Gmail to Google Sheets—in one place.

0
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install luqmannurhakimbazman-ashford@luqmannurhakimbazman/ashford
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:luqmannurhakimbazman/ashford") and the paste-ready config with skillselion.get_install_config("plugin:luqmannurhakimbazman/ashford").

About

What it does

luqmannurhakimbazman-ashford is a community Claude Code plugin marketplace for solo builders who want a fuller agent stack: slash commands, subagents, packaged skills, and MCP server wiring in one catalog. It fits the build phase when you are connecting Claude to real apps—spreadsheets, trackers, and general application development—without writing every integration from scratch. The readme highlights domain-agnostic workflows, hooks, and server configs; keywords suggest utilities from learning trackers to Gmail-to-Google-Sheets bridges. Treat it as a picker menu of three plugins you enable selectively per project. Confidence is moderate because individual plugin names are keyword-derived rather than fully documented here, but the marketplace shape and MCP emphasis are clear. Prefer Ashford when you are standardizing how Claude Code talks to external systems during development.

Highlights

  • Marketplace lists 3 plugins spanning commands, agents, skills, and MCP server configurations.
  • Domain-agnostic development focus with hooks, trackers, and enhanced workflow keywords.
  • Surfaces integrations such as gmailtogooglesheets and dotlinearnetwork-style automation.
  • Community-sourced bundle suitable for experimenting with Aerion, Dunk, Egg, and learning-oriented agents.
  • Single install path for multiple Claude Code extensions instead of separate repos per tool.

Why builders use it

Builders juggling separate repos for MCP servers, custom commands, and skills lose coherence when Claude Code needs one integrated automation surface.

After registering ashford, you can enable up to three community plugins that unify agent skills, hooks, and MCP-backed workflows from a single marketplace.

At a glance

  • Type - Plugin in Automation.
  • Adoption - 0 installs, 0 stars, 0 votes.

FAQ

Who is luqmannurhakimbazman-ashford for?

It is for indie and small-team builders using Claude Code who want commands, agents, skills, and MCP servers discoverable from one ashford marketplace.

When should I use luqmannurhakimbazman-ashford?

Use it during build-phase integration work when you need to wire Claude to external apps, hooks, or spreadsheet workflows via packaged plugins.

How do I add luqmannurhakimbazman-ashford to my agent?

Add the luqmannurhakimbazman/ashford repository as a Claude Code plugin marketplace, review the three available plugins, and enable only those that match your MCP and workflow needs.

Discussion

Comments

Share how you use luqmannurhakimbazman-ashford, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.