Skip to content
Back to skills

Si Intake

ASecurity

Use only when a selected Selective Intelligence Council has unresolved competing interpretations and assigns a bounded intake challenge.

  • 5 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 15, 2026
developmentgo

Works with

  • cli

Security analysis

A100/100

Scanned October 15, 2026

npx -y skills add flavorgood/Selective-Intelligence --skill si-intake --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Si Intake?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Si Intake
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/flavorgood-si-intake/badge)](https://www.skillsdirectory.com/skills/flavorgood-si-intake)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: si-intake
description: Use only when a selected Selective Intelligence Council has unresolved competing interpretations and assigns a bounded intake challenge.
---

# SI Sub-Skill: Intake

## What this skill does (plain language)
It resolves competing meanings and turns the material result into a short packet. Ordinary clear requests stay in the parent context.

## Inputs
- A user message that starts a project
- Optional seed: idea, URL, repo note, image, or short brief

## How it works
1. Read the seed and infer the biggest real goal.
2. If the goal is not in the current message, inspect the available conversation, project/workspace, repository, connected sources, and tools before asking anything.
3. If discovery finds no goal or project at all, return the bounded active-but-empty status from the parent skill. Do not ask a generic outcome question.
4. Save any plain, reversible assumption used to continue.
5. Return a one-screen Intake Packet:
   - Project name (or temporary name if not given)
   - Seed summary
   - What is definitely true vs what is still guessed
   - One next step for the planner

## Output
Return:
- `outcome` (plain sentence)
- `assumptions` (very short list)
- `constraints` (hard limits like safety, money, permissions)
- `next_skill`: `si-planner`
- `next_step_id`

## Non-negotiable rules
- Ask only when a material product, safety, money, or permission decision cannot be recovered from evidence.
- Never ask for keys, tokens, CLI commands, or auth setup in this phase.
- Keep language simple and easy for non-developers.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.