What does the Crud Completeness AI skill do?

Use when implementing complete CRUD operations, including Create, Read, Update, Delete patterns with proper validation, error handling, and business logic. Includes soft delete, restore, bulk operations, and CRUD best practices. Based on enterprise application patterns and API design standards.

Why use Crud Completeness on TypingMind?

Because you install it once and use it with any model. Crud Completeness is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Crud Completeness in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/crud-completeness. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Crud Completeness?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Crud Completeness?

As many as you like. As long as a model supports skills, you can use Crud Completeness with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Crud Completeness AI skill free?

Yes. It is published on GitHub by Omar-Obando under the MIT license. You only pay your own AI provider for the tokens you use.

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Crud Completeness by Omar-Obando — AI Skill for Any LLM

CRUD Completeness Skill — Tech Lead

Overview

This skill provides comprehensive guidance for implementing complete CRUD (Create, Read, Update, Delete) operations. It covers validation, error handling, soft delete, restore, bulk operations, and CRUD best practices following enterprise application patterns and API design standards.

When to Use

Use this skill when:

Implementing complete CRUD operations for resources
Designing Create, Read, Update, Delete endpoints
Adding validation to CRUD operations
Implementing error handling for CRUD
Designing soft delete patterns
Implementing restore functionality
Creating bulk CRUD operations
Adding optimistic concurrency control
Implementing CRUD permissions
Designing CRUD API documentation
Adding audit logging to CRUD
Implementing CRUD caching strategies
Creating CRUD validation schemas
Designing CRUD response formats
Implementing CRUD rate limiting
Adding CRUD metrics and monitoring
Designing CRUD security controls
Implementing CRUD data validation
Creating CRUD input validation
Adding CRUD output formatting
Designing CRUD pagination
Implementing CRUD filtering
Adding CRUD sorting

Do NOT use this skill when:

Writing application business logic (use domain-driven skill)
Designing database schemas (use database-design skill)
Writing API endpoint specifications (use api-design skill)
Performing security audits (use security-auditor skill)
Writing SQL queries (use sql-best-practices skill)
Designing multi-page website layouts (use design-system skill)
Analyzing deployment configurations (use deployment skill)
Writing documentation (use documentation-best-practices skill)

CRUD Operations

Complete CRUD Endpoint Set


┌─────────────────────────────────────────────────────────────┐
│              Complete CRUD Endpoints                        │
├─────────────────────────────────────────────────────────────┤
│  CREATE:  POST   /api/v1/resources                         │
│  READ:    GET    /api/v1/resources                         │
│  READ:    GET    /api/v1/resources/:id                     │
│  UPDATE:  PATCH  /api/v1/resources/:id                     │
│  REPLACE: PUT    /api/v1/resources/:id                     │
│  DELETE:  DELETE /api/v1/resources/:id                     │
│  RESTORE: POST   /api/v1/resources/:id/restore             │
│  BULK:    POST   /api/v1/resources/bulk                    │
│  BULK:    PATCH  /api/v1/resources/bulk                    │
│  BULK:    DELETE /api/v1/resources/bulk                    │
└─────────────────────────────────────────────────────────────┘

CRUD Request/Response Patterns


┌─────────────────────────────────────────────────────────────┐
│              CRUD Request/Response                          │
├─────────────────────────────────────────────────────────────┤
│  CREATE                                                     │
│  POST /api/v1/resources                                     │
│  Request:  { name, description, ... }                       │
│  Response: 201 { data: resource, meta: { requestId } }      │
│                                                              │
│  READ (List)                                                │
│  GET /api/v1/resources?filter[status]=active&sort=-createdAt│
│  Response: 200 { data: [...], pagination: {...} }           │
│                                                              │
│  READ (Detail)                                              │
│  GET /api/v1/resources/:id?include=related                  │
│  Response: 200 { data: resource, included: [...] }          │
│                                                              │
│  UPDATE                                                     │
│  PATCH /api/v1/resources/:id                                │
│  Request:  { name: "Updated" }                              │
│  Response: 200 { data: resource }                           │
│                                                              │
│  DELETE (Soft)                                              │
│  DELETE /api/v1/resources/:id                               │
│  Response: 200 { data: { deleted: true } }                  │
│                                                              │
│  RESTORE                                                    │
│  POST /api/v1/resources/:id/restore                         │
│  Response: 200 { data: resource }                           │
└─────────────────────────────────────────────────────────────┘

Validation Patterns

CRUD Validation Schema

typescript
// Create validation
const createSchema = z.object({
  name: z.string().min(1).max(100),
  description: z.string().max(1000).optional(),
  status: z.enum(['active', 'inactive', 'pending']).default('pending'),
  priority: z.number().int().min(1).max(5).optional(),
  tags: z.array(z.string()).max(10).optional(),
});

// Update validation
const updateSchema = z.object({
  name: z.string().min(1).max(100).optional(),
  description: z.string().max(1000).optional(),
  status: z.enum(['active', 'inactive', 'pending']).optional(),
  priority: z.number().int().min(1).max(5).optional(),
  tags: z.array(z.string()).max(10).optional(),
});

Validation Error Response

json
{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Invalid input data",
    "details": [
      {
        "field": "name",
        "message": "Name must be between 1 and 100 characters"
      },
      {
        "field": "priority",
        "message": "Priority must be between 1 and 5"
      }
    ]
  },
  "meta": {
    "requestId": "req_123",
    "timestamp": "2024-01-15T10:30:00Z"
  }
}

Soft Delete Pattern

Soft Delete Implementation

typescript
// Database schema
interface Resource {
  id: string;
  name: string;
  description?: string;
  status: 'active' | 'inactive' | 'deleted';
  deletedAt?: Date;
  deletedBy?: string;
  createdAt: Date;
  updatedAt: Date;
}

// Soft delete query
const softDelete = async (id: string, userId: string) => {
  return await db.resource.update({
    where: { id },
    data: {
      status: 'deleted',
      deletedAt: new Date(),
      deletedBy: userId,
    },
  });
};

// Restore query
const restore = async (id: string) => {
  return await db.resource.update({
    where: { id },
    data: {
      status: 'active',
      deletedAt: null,
      deletedBy: null,
    },
  });
};

// Soft delete scope
const activeResources = async () => {
  return await db.resource.findMany({
    where: { status: 'active' },
  });
};

Soft Delete API


┌─────────────────────────────────────────────────────────────┐
│              Soft Delete API                                │
├─────────────────────────────────────────────────────────────┤
│  DELETE /api/v1/resources/:id                               │
│  └── Status: 200                                            │
│  └── Body: { data: { deleted: true } }                      │
│                                                              │
│  POST /api/v1/resources/:id/restore                         │
│  └── Status: 200                                            │
│  └── Body: { data: resource }                               │
│                                                              │
│  GET /api/v1/resources?include=deleted                      │
│  └── Status: 200                                            │
│  └── Body: { data: [...], includes: [...] }                 │
│                                                              │
│  DELETE /api/v1/resources/:id/force                         │
│  └── Status: 204 (No Content)                               │
│  └── Permanently deletes record                             │
└─────────────────────────────────────────────────────────────┘

Bulk Operations

Bulk CRUD Pattern

typescript
// Bulk create
POST /api/v1/resources/bulk
Body: { resources: [{ name: "Item 1" }, { name: "Item 2" }] }
Response: 201 { data: [resource1, resource2] }

// Bulk update
PATCH /api/v1/resources/bulk
Body: { resources: [{ id: "1", name: "Updated 1" }] }
Response: 200 { data: [resource1] }

// Bulk delete
DELETE /api/v1/resources/bulk
Body: { ids: ["1", "2", "3"] }
Response: 200 { data: { deleted: 3 } }

Error Handling

CRUD Error Codes


┌─────────────────────────────────────────────────────────────┐
│              CRUD Error Codes                               │
├─────────────────────────────────────────────────────────────┤
│  CREATE                                                     │
│  └── 400: Validation error                                  │
│  └── 401: Unauthorized                                      │
│  └── 403: Forbidden                                         │
│  └── 409: Duplicate resource                                │
│                                                              │
│  READ                                                       │
│  └── 401: Unauthorized                                      │
│  └── 403: Forbidden                                         │
│  └── 404: Resource not found                                │
│                                                              │
│  UPDATE                                                     │
│  └── 400: Validation error                                  │
│  └── 401: Unauthorized                                      │
│  └── 403: Forbidden                                         │
│  └── 404: Resource not found                                │
│  └── 409: Conflict (version mismatch)                       │
│                                                              │
│  DELETE                                                     │
│  └── 401: Unauthorized                                      │
│  └── 403: Forbidden                                         │
│  └── 404: Resource not found                                │
│  └── 409: Conflict (dependency exists)                      │
└─────────────────────────────────────────────────────────────┘

Optimistic Concurrency

ETag Pattern

typescript
// GET returns ETag
Response Headers:
ETag: "abc123"

// UPDATE includes If-Match
Request Headers:
If-Match: "abc123"

// Response for conflict
Status: 409 Conflict
Body: {
  error: {
    code: "CONFLICT",
    message: "Resource was modified by another user"
  }
}

Real-World Impact

Before this skill:

Incomplete CRUD operations
Missing validation
Poor error handling
No soft delete
Inconsistent API

After this skill:

Complete CRUD operations
Proper validation and error handling
Soft delete with restore
Consistent API patterns

Cross-References

api-design - For API endpoint specifications
database-design - For database schema design
security-auditor - For CRUD security review

Publisher	Omar-Obando
Repository	`qwen-orchestrator`
Skill name	`crud-completeness`
Stars	53
Forks	13
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Crud Completeness

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

CRUD Completeness Skill — Tech Lead

Overview

When to Use

CRUD Operations

Complete CRUD Endpoint Set

CRUD Request/Response Patterns

Validation Patterns

CRUD Validation Schema

Validation Error Response

Soft Delete Pattern

Soft Delete Implementation

Soft Delete API

Bulk Operations

Bulk CRUD Pattern

Error Handling

CRUD Error Codes

Optimistic Concurrency

ETag Pattern

Real-World Impact

Cross-References

References

Frequently asked questions

Set up your own AI workspace now

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

CRUD Completeness Skill — Tech Lead

Overview

When to Use

CRUD Operations

Complete CRUD Endpoint Set

CRUD Request/Response Patterns

Validation Patterns

CRUD Validation Schema

Validation Error Response

Soft Delete Pattern

Soft Delete Implementation

Soft Delete API

Bulk Operations

Bulk CRUD Pattern

Error Handling

CRUD Error Codes

Optimistic Concurrency

ETag Pattern

Real-World Impact

Cross-References

References

Frequently asked questions

Related AI Skills

Set up your own AI workspace now