coconala-intake-router-ja

Analyzes Coconala messages to determine route, state, service fit, risk, gaps and next actions for intake workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/riffluv/work1 --skill coconala-intake-router-ja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coconala-intake-router-ja
Source: https://github.com/riffluv/work1/tree/main/.codex/skills/coconala-intake-router-ja
Command: npx skills add https://github.com/riffluv/work1 --skill coconala-intake-router-ja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coconala conversations often require a structured intake before drafting replies. This skill standardizes incoming messages by structuring them into route decisions, current state, service fit, risk indicators, information gaps, and next actions to stabilize the pre-reply context.

Core Features & Use Cases

  • Structured intake: analyzes incoming messages and outputs a defined intake state for downstream skills.
  • Risk-aware framing: flags potential policy issues, missing information, and scope constraints before reply generation.
  • Pre-reply alignment: fixes upstream contracts for subsequent reply synthesis, ensuring consistency across interactions.

Quick Start

Provide an incoming Coconala message and any available user details; the system will produce a structured intake decision.

Frequently Asked Questions about coconala-intake-router-ja

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure incoming Coconala messages before drafting a reply?

Coconala message intake structuring analyzes incoming conversations to determine route decisions, current state, service fit, risk indicators, and information gaps. This standardized pre-reply process stabilizes upstream context for consistent downstream reply generation.

What is pre-reply alignment for Coconala conversation workflows?

Pre-reply alignment for Coconala workflows fixes upstream contracts by structuring incoming messages into defined intake states. This ensures consistent routing decisions and risk-aware framing before any reply synthesis occurs across human handoffs or automated briefings.

How do I identify risk indicators and missing information in Coconala conversations?

Risk-aware framing flags potential policy issues, missing information, and scope constraints in Coconala messages before reply generation. The system outputs a structured intake decision highlighting these risk indicators to support safe reply planning and human handoffs.

Does Coconala message intake routing work with predefined templates?

Yes, Coconala message intake routing relies on predefined templates and routing tables to maintain consistent upstream behavior. It structurally analyzes incoming messages to determine route, state, service fit, and next actions for standardized intake across conversations.

Can I use structured intake decisions to support human handoffs in Coconala?

Structured intake decisions support human handoffs in Coconala by providing a defined intake state that includes route, risk indicators, and next actions. This standardized briefing format ensures safe reply planning and consistent context transfer between team members.

What are the limitations of using predefined routing tables for Coconala intake?

Predefined routing tables for Coconala intake maintain consistent behavior but require available user details and incoming message context to produce accurate decisions. The skill depends on these predefined templates and may not handle novel scenarios outside the defined routing structure.