本文へ移動
cccskills
無料GitHub で公開

structure

Use when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Structuring Engine

A common leverage point: inputs arrive without structured context, defined outcomes, or clear goals. This skill fixes that before any work begins. Frame first, then act (or delegate).

When to run

  • A new task lands fuzzy ("the boss wants the draft checked", "look into the X thing").
  • A long email/chat thread needs to become an action.
  • The user is about to do something the old way → apply the Default Shift ("to what extent could AI be leveraged here?").

The output (always this shape)

## <short title>
**Context** — what's going on, in 2-4 plain sentences. The why behind the ask.
**Desired outcome** — the end state. What does "done" look like, concretely?
**Goal** — the measurable/observable target (a date, a number, a deliverable). One line.
**Owner** — who should own this (route to the team; don't pool on the user by default).
**Next step** — the single next physical action, and by when.
**Decision needed** — the specific call the user must make, framed as a fast choice.

When a decision is involved, present it as a fast checklist they can answer in seconds:

- Send to the client now (yes/no)?
- Loop in <reviewer> first (yes/no)?
- Target date: <propose one>

Process

  1. Read everything given. If it references a ticket, doc, or thread and a connection exists, pull it rather than guessing.
  2. Strip to the real ask. Separate noise from the actual decision/outcome. Name what's missing.
  3. Fill the template. Be concrete. If a field is genuinely unknown, write ❓ <the open question> → <who can answer> instead of inventing.
  4. Route the owner. Default to delegating to the right teammate; only put the user as owner when it's truly theirs (a decision, an external sign-off).
  5. Offer the next move. After the brief, offer to: create the artifact (ticket / note / plan — allowed without approval), draft the reply in the user's voice (internal may send to team; never external without approval), and/or log a decision to decisions/log.md.

Guardrails (from CLAUDE.md)

  • No confidential figures or sensitive/regulated data persisted to the repo. Pull live, don't store.
  • Cite, don't invent — any regulatory/financial/legal claim cites a source or is flagged as a gap.
  • Draft, never send external. Internal to the team may be OK; external needs approval.
  • Match references/voice.md.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

audit

無料

Use when someone asks for an AIOS audit, asks to score their setup against the Four Cs, or says "is my AIOS working" / "audit my setup" / "find gaps in my AIOS". Produces a Four-Cs scoreboard with top-3 fixes ranked by leverage.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/gaios462026年6月7日 更新

daily

無料

Use at the start of a working day (or when the user asks "what should I focus on today / give me my brief / daily standup"). Produces a one-screen daily brief — today's top 3, open loops that need a nudge, what's slipping, and a suggested focus order. Trigger on "/daily", "daily brief", "what should I focus on today", "morning brief", "standup".

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/gaios462026年6月7日 更新

decide

無料

Use when the user faces a real decision with stakes and wants it framed cleanly — options, ranked criteria, a recommendation, the falsifier, and reversibility — then logged to decisions/log.md. Trigger on "/decide", "help me decide", "should I X or Y", "frame this decision", "what's the call here", "log this decision".

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/gaios462026年6月7日 更新

draft

無料

Use when the user needs a written communication drafted in their voice — an email, a Slack/Teams message, a team update, an announcement, a reply to a thread, or a post. Produces a ready-to-review draft matching references/voice.md; never auto-sends external. Trigger on "/draft", "draft an email", "write a reply", "draft the update", "draft the announcement", "respond to this thread in my voice".

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/gaios462026年6月7日 更新

Template skill for a leadership-transition / executive cockpit — when someone steps into or covers a leadership role and needs to not drop anything. Produces a handoff doc + decision-rights map, an "open loops" tracker, a team-comms cadence, and a recurring report/update drafter. Trigger on "/exec-cockpit", "handoff doc", "decision-rights map", "open loops tracker", "cover for <role>", "interim <role>". Customize the placeholders to your situation.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/gaios462026年6月7日 更新

Use to run an autoresearch-style experiment loop — improve a measurable artifact by trying changes, measuring against one objective metric, keeping if better and reverting if not, on an isolated git branch with a logged trail. Trigger on "/experiment", "run an experiment loop", "autoresearch X", "tune/optimize X against a metric", "hill-climb X". Follows references/sops/experiment-loop.md. Enforces the autonomy gate (objective metric + reversible sandbox + no PHI/external) before any unsupervised looping.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/gaios462026年6月7日 更新

alirezarezvani のスキルをすべて見る

このスキルの問題を報告する