القائمة
Generate intelligent session IDs based on detected content source type. Analyzes ContentSummary and creates meaningful IDs (podcast-xyz, transcript-abc, etc.).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | id-generator |
| description | Generate intelligent session IDs based on detected content source type. Analyzes ContentSummary and creates meaningful IDs (podcast-xyz, transcript-abc, etc.). |
Expert at generating meaningful session IDs based on content source type and characteristics.
Follow these 5 steps:
{source-type}-{date}-{topic}podcast-2024-12-08-ai-healthcarecontentId: Generated IDdetectedSource: Confirmed source typesourceConfidence: 0.0-1.0 confidence in source detectionrationale: Brief explanation of why this source typepodcast-{date}-{topic}transcript-{date}-{topic}article-{date}-{topic}youtube-{date}-{topic}tweet-{date}-{topic}text-{date}-{topic}content-{date}-{topic}Input: Podcast about AI in Healthcare (2024-12-08)
Output: podcast-2024-12-08-ai-healthcare
Input: Whisper transcript of React conference talk (2024-12-07)
Output: transcript-2024-12-07-react-conference
Input: Article on productivity hacks (2024-12-06)
Output: article-2024-12-06-productivity-hacks
Input: YouTube tutorial on Python (2024-12-05)
Output: youtube-2024-12-05-python-tutorial
Return structured JSON:
{
"contentId": "podcast-2024-12-08-ai-healthcare",
"detectedSource": "podcast",
"sourceConfidence": 0.95,
"rationale": "Audio transcript with speaker markers, timestamps, and conversational flow indicates podcast source."
}
End-to-end testing for looplia CLI from local source. Builds the CLI, initializes workspace, runs the writing-kit workflow, and verifies outputs. Use when testing local development or validating workflow execution.
This skill should be used when the user wants to execute a looplia workflow, run workflow steps, or process a workflow.md file. Use when someone says "run the looplia workflow", "execute this looplia pipeline", "/run writing-kit", "start the looplia automation", or "process these workflow steps". Architecture: One workflow step triggers one general-purpose subagent call, which then invokes skills to accomplish the step's mission. Each step = separate context window. Handles sandbox management, per-step orchestration, and validation state tracking. v0.6.9: Unified general-purpose subagent strategy for all providers (context offload).
Bump version across all looplia-core package.json files, changelog, and documentation. Use when: releasing a new version, preparing a version bump PR, updating version numbers across the monorepo. Handles all 5 package.json files, CHANGELOG.md, docs/README.md, and the landing page version badge.
This skill should be used when the user wants to create a new looplia workflow, generate a workflow definition file, or compose workflow steps from skill recommendations. Use when someone says "create a looplia workflow", "generate workflow.md", "compose workflow steps", "build me an automation pipeline", or "/build" (final step). Final step in looplia workflow building: transforms skill recommendations into valid v0.7.0 workflow YAML/Markdown files. Each step uses skill: + mission: syntax, following the one workflow step → one skill-executor → multiple skills architecture. v0.7.0: Generates explicit `skills:` declaration for selective plugin loading. v0.6.3: Supports input-less workflows using input-less capable skills (e.g., search).
Load the skill catalog for workflow building. This skill should be used when discovering available looplia skills or listing what capabilities are available. Use when someone says "what looplia skills are installed", "list available skills", "/build", "what can looplia do", or "show me all looplia capabilities". v0.7.0: Replaces plugin-registry-scanner with skill catalog for faster access. Auto-syncs from all sources on every build to ensure freshest skill catalog.
This skill should be used when matching user requirements to available skills from a compiled registry. It receives a skill registry (from registry-loader) and user requirements, then scores each skill based on capability alignment, producing prioritized matches with confidence scores. Triggers: "match skills to requirements", "find relevant skills for workflow", "which skill handles X", "score skill capabilities", "/build" (after registry load), "find skills for this task", "match my requirements to skills". Second step in looplia workflow building pipeline: takes user requirements and skill registry, recommends skill sequences with missions. Designs one workflow step → one skill-executor → multiple skills orchestration pattern.