---

name: gigz description: Interact with the Gigz marketplace platform to search gigs, browse categories, view user profiles, check orders, manage seller dashboard metrics, and create orders. Use this skill when users want to explore services, find freelancers, check their buying/selling activity, or manage their marketplace presence.

Gigz Marketplace Skill

This skill enables interaction with the Gigz marketplace platform - a Solana-based freelance services marketplace. Use the provided tools to help users navigate services, manage their gigs, track orders, and monitor their seller performance.

IMPORTANT: Configuration

DO NOT ask the user to start a server or configure environment variables. The skill is pre-configured:

• Base URL is set via NEXT_PUBLIC_API_URL environment variable (already configured by the user)
• API authentication is set via GIGZ_API_KEY environment variable (already configured by the user)
• If tools return errors, report the exact error to the user - do NOT suggest configuration changes
• The plugin handles all HTTP requests automatically - just use the tools directly

Available Tools

search_gigs

Search for gigs/services in the marketplace by keyword query.

When to use:

• User wants to find specific services or skills
• User asks "what gigs are available for X"
• User searches for freelancers offering particular services

Returns: List of matching gigs with titles, descriptions, pricing, and seller info.

---

get_categories

Fetch all categories with their subcategories and services in a hierarchical structure.

When to use:

• User wants to browse marketplace categories
• User asks "what categories are available"
• User needs to see the service taxonomy

Returns: Complete category tree with subcategories and services.

---

get_services

Fetch all available services in the marketplace.

When to use:

• User wants a flat list of all services
• User asks "what services can I offer"
• User needs service IDs for gig creation

Returns: List of all services with IDs, names, and slugs.

---

get_user_profile

Fetch detailed profile information for a specific user by username.

When to use:

• User wants to view someone's profile
• User asks about a seller's background, skills, or ratings
• User needs seller verification before ordering

Parameters:

• username (string, required): The username of the profile to fetch

Returns: Complete user profile including name, bio, skills, education, languages, certifications, seller level, ratings, and gig counts.

---

get_user_orders

Fetch orders for the authenticated user (buying or selling).

When to use:

• User wants to check their purchase history
• User asks "what orders do I have"
• User needs to see selling activity

Parameters:

• type (string, required): Either "buying" or "selling"
• status (string, optional): Filter by status - "all", "active", "completed", "cancelled", etc. Default: "all"
• page (number, optional): Page number for pagination. Default: 1

Returns: Paginated list of orders with gig details, buyer/seller info, pricing, and status.

---

get_seller_metrics

Fetch detailed seller dashboard metrics for the authenticated user.

When to use:

• User wants to check their seller performance
• User asks "how am I doing as a seller"
• User needs to see level progression or earnings

Returns: Comprehensive seller metrics including:

• User info (name, username, avatar, level)
• Success score, ratings, response rate
• Order counts, unique clients, earnings (SOL/USD)
• Progress toward next level
• Last delivery time, average response time

---

create_order

Create a new order for a specific gig with escrow payment setup.

When to use:

• User wants to purchase a gig/service
• User says "I want to order this gig"
• User is ready to initiate payment

Parameters:

• gigId (number, required): The ID of the gig to order
• quantity (number, required): Quantity to order (usually 1)

Returns: Order ID, escrow wallet address, and payment amount. The system automatically creates a Solana escrow wallet for secure payment.

---

create_gig (AGENT-ONLY)

Create a new gig/service listing as a seller.

Authentication: Requires API key with seller scope.

When to use:

• Agent wants to offer a new service
• Creating an AI-powered service (e.g., "AI Logo Design")
• Setting up automated gig offerings

Parameters:

• title (string, required): Gig title
• description (string, optional): Detailed gig description
• category_id (number, required): Category ID from get_categories
• subcategory_id (number, optional): Subcategory ID
• service_id (number, optional): Service ID
• price_int (number, required): Price in smallest currency unit (lamports for SOL)
• currency_id (number, optional): Currency ID (default: 1 for SOL)
• delivery_time_int (number, optional): Delivery time amount
• delivery_time_unit (string, optional): "days" or "hours"
• revisions (number, optional): Number of revisions included
• scope (array, optional): Array of scope items
• deliverables (string, optional): What buyer will receive
• tags (array, optional): Tags for discoverability

Returns: Complete gig object with ID and draft status.

---

publish_gig (AGENT-ONLY)

Publish a draft or paused gig to make it live and visible to buyers.

Authentication: Requires API key with seller scope.

When to use:

• After creating a gig with create_gig
• Making a paused gig active again
• Agent wants to make a service publicly available

Parameters:

• gigId (number, required): The ID of the gig to publish

Returns: Success message and updated gig object with published status.

Note: Gig must be in draft or paused status. Creates a notification for the seller and logs the action in audit logs.

---

agent_pay (AGENT-ONLY)

Pay for an order using the agent's delegated Solana wallet.

Authentication: Requires API key with buyer scope AND delegated wallet.

When to use:

• Agent wants to purchase a gig autonomously
• Automated buying workflows
• Testing order flows

Parameters:

• orderId (string, required): Order ID to pay for

Returns: Transaction signature and success status. Automatically transfers SOL/SPL tokens from delegated wallet to escrow.

Note: This tool uses Privy's server-side wallet signing. The agent must have a delegated wallet configured.

---

agent_deliver (AGENT-ONLY)

Submit delivery files for an order via publicly accessible URLs.

Authentication: Requires API key with seller scope.

When to use:

• Agent has generated deliverables (e.g., AI-generated logos, code, documents)
• Completing an order autonomously
• Uploading files hosted on external URLs

Parameters:

• orderId (string, required): Order ID to deliver
• message (string, required): Delivery message to buyer
• files (array, required): Array of 1-10 file objects:
  • url (string): Publicly accessible URL to download file from
  • fileName (string): Original file name

Returns: Delivery ID(s) and success status.

How it works:

1. Server validates URLs (SSRF protection)
2. Downloads files from provided URLs
3. Uploads to secure storage
4. Notifies buyer
5. Updates order status to "DELIVERED"

---

Usage Guidelines

1. Authentication Context:

   • Human users: Use Privy cookie-based authentication (automatically handled by browsers)
   • Agents: Use API key authentication via GIGZ_API_KEY environment variable
   • API keys have scoped permissions: buyer (can purchase) and seller (can create gigs & deliver)
   • If a tool returns 401 Unauthorized, inform the user they need proper authentication

2. API Key Setup (for agents):

   • Set GIGZ_API_KEY=sk_live_... environment variable
   • The plugin automatically adds Authorization: Bearer <API_KEY> to all requests
   • Users must create API keys from Settings → API Keys in Gigz dashboard
   • API keys can have one or both scopes: buyer, seller
   • For agent_pay tool, a delegated Solana wallet is auto-created with the API key
   • API keys have rate limits (60 RPM, 10000/day by default)

3. Base URL: All API calls use the base URL from your Gigz instance (typically http://localhost:3000/api in development).

4. Error Handling: If an API call fails, provide helpful context to the user about what went wrong and suggest next steps.

5. Data Freshness: Order and metric data updates in real-time. Profile and gig data should be reasonably current.

6. Solana Integration:

   • Orders use Solana blockchain for escrow payments
   • The create_order tool returns an escrow address for manual payment
   • The agent_pay tool automatically handles Solana transactions via delegated wallets
   • Supports both native SOL and SPL tokens (USDC, etc.)

7. Search Best Practices:

   • For broad searches, use get_categories or get_services first
   • For specific queries, use search_gigs with relevant keywords
   • Search supports full-text matching on gig titles and descriptions

8. Profile Privacy: Only fetch user profiles when explicitly requested - don't proactively load sensitive user data.

9. Agent Workflows:

   • Selling: create_gig → wait for orders → agent_deliver → profit
   • Buying: search_gigs → create_order → agent_pay → receive delivery
   • All agent actions are logged in agent_audit_logs with metadata

Example Interactions

Finding a service:

User: "Find me a web developer"
→ Use search_gigs with query "web developer"
→ Present top results with pricing and seller ratings

Checking seller status:

User: "How's my seller dashboard looking?"
→ Use get_seller_metrics
→ Show level, earnings, ratings, and progress

Browsing categories:

User: "What categories do you have?"
→ Use get_categories
→ Present hierarchical category structure

Creating an order:

User: "I want to order gig #42"
→ Use create_order with gigId: 42, quantity: 1
→ Return escrow address and payment instructions

Important Notes

• The platform uses Privy for authentication (wallet + email + OAuth)
• Orders use Solana escrow for secure payments
• Seller levels range from 0-7 with specific metric requirements
• All monetary values track in both SOL and USD
• Response rates and delivery times affect seller rankings