resource-prompt-patterns

Generate MCP resource and prompt patterns for Rust Turul projects.

2|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/aussierobots/turul-mcp-framework --skill resource-prompt-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resource-prompt-patterns
Source: https://github.com/aussierobots/turul-mcp-framework/tree/main/plugins/turul-mcp-skills/skills/resource-prompt-patterns
Command: npx skills add https://github.com/aussierobots/turul-mcp-framework --skill resource-prompt-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides standardized patterns for creating MCP resources and prompts in Turul MCP Framework, reducing boilerplate and promoting consistency across tooling patterns.

Core Features & Use Cases

  • Pattern coverage across Function Macro #[mcp_resource], Derive Macro #[derive(McpResource)], Declarative macro resource!{}, and ResourceBuilder for resources; and Derive McpPrompt, declarative prompt!, and PromptBuilder for prompts.
  • Real-world use cases include rapid scaffolding of MCP resources and prompts with consistent metadata generation and registration.

Quick Start

Choose a pattern that matches your needs, then register it with McpServer::builder().resource(...) or .prompt(...), and run your server.

Frequently Asked Questions about resource-prompt-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create MCP resources and prompts in Rust without writing boilerplate?

You can create MCP resources and prompts using reusable pattern templates including function macros, derive macros, declarative macros, and runtime builders. These patterns generate consistent metadata and registration scaffolding for Turul MCP projects.

What patterns are available for defining MCP resources in the Turul framework?

MCP resources support four pattern types: the function macro #[mcp_resource], the derive macro #[derive(McpResource)], the declarative macro resource!{}, and a ResourceBuilder for runtime construction.

How do I register MCP resources and prompts after defining them?

After choosing and defining a pattern, register it with McpServer by calling McpServer::builder().resource(...) for resources or .prompt(...) for prompts, then run your server.

Can I use derive macros for MCP prompts, or are they only for resources?

Derive macros support both. You can use #[derive(McpPrompt)] for prompts alongside declarative prompt! macros and PromptBuilder, providing the same pattern coverage as resources.

What's the best way to ensure consistent metadata generation across MCP tooling patterns?

Applying standardized pattern templates for resources and prompts ensures consistent metadata generation and registration, reducing boilerplate and promoting uniformity across Turul MCP development workflows.

Do I need the Turul MCP Framework to use these resource and prompt patterns?

Yes, these pattern templates are designed specifically for Rust Turul MCP projects, providing scaffolding and metadata generation tailored to the Turul framework's server builder registration system.