Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

raven-sync

Estrelas5

Forks1

Atualizado14 de maio de 2026 às 23:48

Use when requirements.txt or pyproject.toml has changed and you want to sync all libraries into manifest.json. CVE checks each one. Approved libraries are auto-added. Blocked ones are flagged. Run after pip install or when onboarding a new project.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

giggsoinc

giggsoinc/raven

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de segurança da informaçãoInformática e Matemática·SOC 15-1212

SKILL.md

readonly

name	raven-sync
description	Use when requirements.txt or pyproject.toml has changed and you want to sync all libraries into manifest.json. CVE checks each one. Approved libraries are auto-added. Blocked ones are flagged. Run after pip install or when onboarding a new project.
allowed-tools	Bash

/raven-sync

Syncs all libraries from requirements files into manifest.json.

Steps

Run: python3 .claude/scripts/sync-libraries.py
Show summary: approved / blocked / skipped
If blocked libs found — report to developer with reason
If all clean — confirm manifest.json updated

Options

/raven-sync — full sync with CVE check
/raven-sync --dry-run — show what would change, don't write
/raven-sync --no-cve — skip CVE check, approve all found libs

When to run

After pip install of new libraries
When onboarding existing project to Raven
After pulling a branch with new dependencies

Mais deste repositório

mesmo repositório

raven-init

giggsoinc/raven

Initialize Raven for a new project. Andie-conversational — auto-scans project, asks at most 2 questions, generates manifest.json, validates, and commits with audit trail.

2026-06-115

andie

giggsoinc/raven

USE PROACTIVELY whenever the user asks for: planning, design, architecture decision, tradeoff analysis, comparing approaches, strategy, system design, refactor scope, deciding what to build, or any non-trivial request needing clarification. Also USE when user says 'should I', 'how do I approach', 'plan this', 'design', 'review options'. Compact plan-first orchestration. Routes work, runs triad (Functional/Technical/Data), HITL gated, OODA loop. Hands off plans, never implements. Brownfield bugs → andie-jr.

2026-06-115

andie-jr

giggsoinc/raven

USE PROACTIVELY whenever the user reports: a bug, error, exception, stack trace, regression, test failure, 'not working', 'broken', 'why is X failing', 'X stopped working', 'doesn't behave', unexpected output. Brownfield debug assistant. Max 2 rounds, max 3 roles, returns problem · root cause · fix · why · audit note · commit suggestion. Do NOT use for greenfield design — that goes to andie.

Tool and product registry for Andie pre-flight. Maps problem types to tool options with tradeoffs. Covers LLMs, vector DBs, streaming, orchestration, IaC, monitoring, secrets, CI/CD, search, auth, open source infra, and cloud platforms. Load when a tool selection decision is in scope.

Execute qualquer Skill com um clique