본문으로 건너뛰기
cccskills
무료GitHub에 공개

apple-notes-core-workflow-a

Use JXA scripts to automate Apple Notes workflows on macOS. This skill helps import Markdown files, create meeting, daily, or project notes from templates, and organize notes into folders using naming rules, with bounded batches and checks for safe reconciliation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Build automated note management workflows with Apple Notes JXA scripts. Use when batch-creating notes, syncing content from external sources, organizing notes into folder hierarchies, or building note templates. Trigger: "apple notes workflow", "batch notes", "note templates", "organize apple notes", "sync notes".

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Importing Markdown files into Apple Notes
  • Creating meeting or project notes from templates
  • Sorting notes into folders by naming rules
  • Planning a small, reviewable bulk note update

포함된 파일(1)

  • SKILL.md6.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Apple Notes Core Workflow A — Note Management Automation

Overview

Primary workflow: automate Apple Notes management with batch creation, template-based note generation, folder organization, and content sync from external sources (Markdown files, RSS, calendar events).

Prerequisites

  • Approved source files, a named target account and pre-created test folder, and a backup/reconciliation plan for bulk changes.
  • Sanitization for external Markdown, feed, or calendar content before it becomes note HTML.
  • A durable source-record key for every import or move so retries can be reconciled.

Instructions

  1. Start with synthetic data in the configured local test folder; do not use a default account or create production folders implicitly.
  2. Validate and sanitize each source record before conversion, then enqueue one mutation at a time with an idempotency key.
  3. Record only opaque source keys and outcomes, inspect a bounded sample, and reconcile counts before widening scope.
  4. Stop on a timeout or unexpected folder match; do not rerun a whole batch blindly.

Procedure

Step 1: Batch Note Creator from Markdown Files

#!/bin/bash
# scripts/markdown-to-notes.sh — Import Markdown files as Apple Notes

FOLDER_NAME="${1:-Imported}"

for md_file in *.md; do
  [ -f "$md_file" ] || continue
  title=$(head -1 "$md_file" | sed 's/^#\s*//')
  # Convert Markdown to basic HTML
  body=$(cat "$md_file" | sed 's/^# /<h1>/;s/$/<\/h1>/' | sed 's/^## /<h2>/;s/$/<\/h2>/' | sed 's/^- /<li>/;s/$/<\/li>/' | sed 's/^$/<br>/')

  osascript -l JavaScript -e "
    const Notes = Application('Notes');
    const account = Notes.defaultAccount;
    let folder = account.folders().find(f => f.name() === '$FOLDER_NAME');
    if (!folder) {
      folder = Notes.Folder({ name: '$FOLDER_NAME' });
      account.folders.push(folder);
    }
    const note = Notes.Note({ name: '$title', body: \`$body\` });
    folder.notes.push(note);
    'Created: $title';
  "
  echo "Imported: $md_file → $title"
done

Step 2: Note Template Engine (JXA)

// scripts/note-template.js — Run with: osascript -l JavaScript scripts/note-template.js
const Notes = Application('Notes');

const TEMPLATES = {
  meeting: (data) => `
    <h1>${data.title || 'Meeting Notes'}</h1>
    <p><strong>Date:</strong> ${new Date().toLocaleDateString()}</p>
    <p><strong>Attendees:</strong> ${data.attendees || 'TBD'}</p>
    <h2>Agenda</h2><ul><li></li></ul>
    <h2>Action Items</h2><ul><li></li></ul>
    <h2>Notes</h2><p></p>
  `,
  daily: (data) => `
    <h1>Daily Log — ${new Date().toLocaleDateString()}</h1>
    <h2>Tasks</h2><ul><li></li></ul>
    <h2>Accomplishments</h2><ul><li></li></ul>
    <h2>Blockers</h2><ul><li></li></ul>
  `,
  project: (data) => `
    <h1>${data.title || 'Project'}</h1>
    <p><strong>Status:</strong> ${data.status || 'Active'}</p>
    <h2>Overview</h2><p></p>
    <h2>Requirements</h2><ul><li></li></ul>
    <h2>Timeline</h2><ul><li></li></ul>
  `,
};

function createFromTemplate(templateName, data, folderName) {
  const template = TEMPLATES[templateName];
  if (!template) throw new Error(`Unknown template: ${templateName}`);

  const account = Notes.defaultAccount;
  let folder = account.folders().find(f => f.name() === folderName);
  if (!folder) {
    folder = Notes.Folder({ name: folderName });
    account.folders.push(folder);
  }

  const body = template(data);
  const note = Notes.Note({ name: data.title || templateName, body });
  folder.notes.push(note);
  return note.id();
}

// Usage: create meeting notes
createFromTemplate('meeting', {
  title: 'Sprint Planning',
  attendees: 'Team Alpha',
}, 'Meetings');

Step 3: Folder Organization Script

# Organize notes into folders based on naming conventions
osascript -l JavaScript -e '
  const Notes = Application("Notes");
  const account = Notes.defaultAccount;
  const allNotes = account.notes();

  const rules = [
    { pattern: /^Meeting:/i, folder: "Meetings" },
    { pattern: /^Project:/i, folder: "Projects" },
    { pattern: /^Daily/i, folder: "Daily Logs" },
    { pattern: /^TODO/i, folder: "Tasks" },
  ];

  let moved = 0;
  for (const note of allNotes) {
    const name = note.name();
    for (const rule of rules) {
      if (rule.pattern.test(name)) {
        let folder = account.folders().find(f => f.name() === rule.folder);
        if (!folder) {
          folder = Notes.Folder({ name: rule.folder });
          account.folders.push(folder);
        }
        Notes.move(note, { to: folder });
        moved++;
        break;
      }
    }
  }
  `Organized ${moved} notes into folders`;
'

Output

  • Batch Markdown file → Apple Notes importer
  • Template engine with meeting/daily/project templates
  • Rule-based folder organization
  • Folder creation on-demand

Error Handling

ErrorCauseSolution
Can't move noteNote is lockedUnlock note in Notes.app first
HTML rendering issuesInvalid HTML tagsUse basic tags: h1, h2, p, ul, li, strong
Slow batch importiCloud sync throttlingAdd 1s delay between note creates
Duplicate notesScript run twiceCheck for existing note by name before creating

Examples

For a migration rehearsal, import five synthetic Markdown files into a pre-created local test folder and reconcile the five source-record keys. For a live organization change, generate a dry-run move plan first, obtain owner approval, then process a small bounded batch rather than moving every matching note at once.

Resources

Next Steps

For exporting and converting notes, see apple-notes-core-workflow-b.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 25일 업데이트

Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 25일 업데이트

Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 25일 업데이트

Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 25일 업데이트

Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 25일 업데이트

Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace2.9천2026년 10월 25일 업데이트

jeremylongshore의 스킬 모두 보기

이 스킬의 문제 신고