# Overview ### What are Claude skills? Claude Skills are packaged sets of instructions and integrations that extend what Claude can do for Mailworks employees. Each skill gives Claude specialized knowledge (brand guidelines, document formats, company processes, tool access) so employees can accomplish real work through natural conversation. Skills are enabled org-wide and Claude applies them automatically across any chat based on the intent of the request. Employees can also call up a specific skill directly using the `/` slash command or the `+` icon in the bottom left of any conversation. *** ### Skill Components A Claude Skill can include up to five types of components but not every skill uses all five. One skill may only need instructions and a reference file. Another skill may need instructions, references, assets, and an MCP server. The components are additive based on what the skill needs to do. 1. **Skill Instructions (SKILL.md)** is the core of every skill and the only required component. It is a markdown file that tells Claude what the skill does, what rules to follow, and how to handle requests. It is uploaded to a Claude Project as a knowledge file. 2. **Reference Files** are supporting documents with detailed specifications. These include brand guides with hex codes and typography rules, process documents with step-by-step procedures, data dictionaries, or any reference material Claude needs to do the job well. 3. **Scripts** are executable code (Python, JavaScript, bash) that Claude runs directly during a conversation. They are used for tasks better handled by code than reasoning, such as data processing, file conversion, calculations, and formatting logic. 4. **Assets** are static files bundled with the skill. These include logo images, document templates, font files, or any resource the skill needs to produce its output. 5. **MCP Server (optional)** is a connection to an external system through the Model Context Protocol. It is required when a skill needs to create, read, update, or delete things outside of Claude, such as Google Docs, Asana tasks, or database records. *** ### How Employees Use Skills Employees use skills by talking to Claude in natural language. They describe what they need and Claude handles the rest, following brand guidelines, formatting rules, and calling external tools as needed. Skills can be made available to employees in two ways: **Organization-wide** skills are configured in the Claude admin settings by an Owner and are available to all employees across all conversations. MCP connectors set up at the org level fall into this category. Any employee can access these tools without being in a specific project. **Project-level** instructions and tools are added to the Project Instructions or Knowledge base of a specific Claude Project. While true Skills (ZIP files) are currently managed at the individual or org level, Project Instructions function as project-specific skills that only employees with access to that project can use. This is useful for department-specific workflows or those still in testing. Some workflows use a combination of both. For example, an MCP connector may be available org-wide to provide data access, while the detailed instructions on how to use that data live within a specific project. Employees do not need to understand the underlying architecture, JSON formats, or MCP protocol. They just talk to Claude. *** ### How Skills Are Built and Maintained Skill development is owned by the CEO with strategic input from the CSO. The CEO determines what skills get built, reviews all output, and approves skills before they are deployed to employees. The designated AI systems architect builds and maintains skills based on direction from the CEO. This includes writing skill instructions, assembling reference files and assets, building any required integrations, testing output quality, and iterating based on feedback. This process is collaborative and will evolve as the skill library grows. All skill files and configuration are documented in this playbook under their respective skill pages. *** ### Skill Index | Skill | Description | MCP Required | Status | | ---------------------- | --------------------------------------------------------------- | ------------ | -------------- | | Mailworks Branded Docs | Create and edit basic branded Google Docs from natural language | Yes | In Development | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://knowledge.themailworks.com/skills/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.