- Home
- Skills
- Abdullahbeam
- Nexus Design Abdullah
- Create Master Skill
create-master-skill_skill
- Python
2
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill abdullahbeam/nexus-design-abdullah --skill create-master-skill- SKILL.md8.5 KB
Overview
This skill creates a reusable master system skill (a shared resource library) for any integration. It guides a project-first workflow: create a planning project, run deep API research, design the shared architecture, build from templates, and validate with tests and a child skill. The result is a single source of truth for setup, API patterns, error handling, and utilities used by multiple related skills.
How this skill works
Ask the user for the integration name, validate it, and create a planning project to organize work. Execute a structured four-phase process: Web Research (gather official docs, auth, rate limits, SDKs), Architecture Design (define child skills, shared resources, and scripts), Build (populate templates adapted to research), and Validate (run config checks, discovery scripts, and create at least one child skill). Each phase produces deliverables that keep the master skill maintainable and testable.
When to use it
- When 3+ skills will share the same integration logic and you want to avoid duplicated content
- Before building new skills that rely on common setup, auth, or error handling
- When you need a centralized place for API patterns, rate limiting, and utility scripts
- When onboarding multiple contributors to a consistent integration standard
- When you want to reduce context size and maintain a single source of truth
Best practices
- Always create a planning project before research or coding to track tasks and findings
- Perform comprehensive web research first: official API docs, endpoints, auth, rate limits, SDKs, and error codes
- Design shared resources from the research: common setup, schemas, errors, and helper scripts
- Adapt templates to the integration—do not copy blindly from prior masters
- Validate with automated checks and at least one child skill that references the master
Example use cases
- Create a master skill for Airtable that provides setup, API reference, discovery scripts, and rate-limit helpers used by query and sync child skills
- Standardize Slack integration patterns (auth, message formats, retry strategies) for multiple workflow skills
- Build a Stripe master skill with shared error-handling and schema definitions for billing and subscription child skills
- Extract common Google Sheets logic into a master skill used by import/export and reporting skills
FAQ
Starting with a planning project captures research findings, defines scope, and prevents rework—complex integrations benefit from organized planning first.
What if the integration already has SDKs or libraries?
Research those SDKs to decide whether to wrap them or use them directly; include installation and version guidance in the master skill.