create-resource

# Create Resource

Create a resource note from an analyzed proposal.

## Input

You receive a proposal object from an analyzer skill:

```json
{
  "file": "00 Inbox/✂️ Article Title.md",
  "type": "clipping|transcription|attachment",
  "proposed_title": "Meaningful Title",
  "proposed_template": "resource",
  "summary": "2-3 sentence summary",
  "categorization_hints": ["hint1", "hint2", "hint3"],
  "area": "[[🌱 Area Name]]",
  "project": "[[🎯 Project Name]]",
  "resourceType": "article|tutorial|reference|thread|video|idea",
  "source_format": "article|video|thread|document|audio",
  "author": "Author Name",
  "source_url": "https://..."
}
```

## Output

Create the resource note and handle the original file.

## Workflow

### Step 0: Discover Template Metadata

Before creating the note, query the resource template for its current structure:

```
para_template_fields({ template: "resource", response_format: "json" })
```

Extract from response:
- `validArgs` → which args to pass to `para_create`
- `creation_meta.dest` → destination folder
- `creation_meta.contentTargets` → section headings for content injection (e.g., `["Layer 1: Captured Notes"]`)
- `creation_meta.sections` → all body section headings

### Step 1: Create Resource Note

**CRITICAL:** Use frontmatter-only approach. ALL data in `args`, NEVER in `content`.

Use discovered `validArgs` for field names and `creation_meta.dest` for destination:

```
para_create({
  template: "resource",
  title: proposal.proposed_title,
  dest: "<discovered-dest>",
  args: {
    summary: proposal.summary,
    source: proposal.source_url,
    resource_type: proposal.resourceType,
    source_format: proposal.source_format,  // Enables 📚🎬 emoji prefix (video, thread, etc.)
    // Single area: pass string directly — "[[🌱 Area]]"
    // Multiple areas: pass JSON array string — '["[[🌱 Area 1]]", "[[🌱 Area 2]]"]'
    areas: Array.isArray(proposal.area) ? JSON.stringify(proposal.area) : proposal.area,
    projects: Array.is