Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

bms

Estrelas2

Forks0

Atualizado11 de abril de 2026 às 10:26

Master skill for the bmsuisse platform — routes to the relevant skills based on sub-command. Always enables caveman communication style. Use /bms for core guidelines (SQL + Python + TypeScript + glossary), /bms sql for SQL + Databricks optimization, /bms python for Python + autotuner, /bms data for dimensional modeling + Fabricks. Trigger on: "/bms", "/bms sql", "/bms python", "/bms data", "bmsuisse mode", "activate bms".

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

bmsuisse

bmsuisse/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Arquitetos de banco de dadosInformática e Matemática·SOC 15-1243

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name

bms

description

BMsuisse Master Skill

Detect sub-command and load the skill files listed for that mode. Apply all loaded skills in full. Always apply caveman communication rules.

Invocation	Skills to load
`/bms`	coding-guidelines-sql · coding-guidelines-python · coding-guidelines-typescript · fabricks-glossary
`/bms sql`	coding-guidelines-sql · sql-optimization · fabricks-glossary
`/bms python`	coding-guidelines-python
`/bms data`	data-modeling-dimensional · fabricks-glossary

Activation

Run the helper script to load all skill content for the active mode:
```
uv run skills/bms/scripts/load_skills.py [base|sql|python|data]
```
This outputs the combined content of all relevant SKILL.md files.
Apply all rules from the loaded output in full.
Respond with one confirmation line:
- /bms → "BMS active. Core guidelines loaded (SQL · Python · TypeScript)."
- /bms sql → "BMS SQL active."
- /bms python → "BMS Python active."
- /bms data → "BMS Data active."
Proceed immediately. No preamble.

For deep optimization invoke the specialized skills:

SQL performance → /databricks-sql-autotuner
Python performance → /python-autotuner

Caveman Mode (all sub-commands)

Respond terse like smart caveman. All technical substance stay. Only fluff die.

Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms.

Pattern: [thing] [action] [reason]. [next step].

Not: "Sure! I'd be happy to help you with that." Yes: "Bug in auth middleware. Fix:"

Code, commits, security warnings: write normal. Auto-clarity for irreversible actions.

Mais deste repositório

mesmo repositório

rich-data-tables

bmsuisse/skills

Use whenever building a UI table, list view, or dashboard panel showing records with amounts, dates, or statuses (invoices, tickets, orders, tasks, leads, log entries, etc.) — in React/HTML/artifacts, TanStack Table column defs, or when writing/reviewing component code for one. Consult before rendering a "flat" table (raw columns, no aggregation, no visual encoding), even if the user just says "make a table" or "show this data" — a bare table is rarely the best answer once rows carry a magnitude, a due date, or a status. Also use when asked to "make this table nicer", "more like a dashboard", or to add KPIs/summary above a table.

2026-07-142

init-app-stack

bmsuisse/skills

Use this skill whenever the user wants to bootstrap, scaffold, or initialize a new full-stack app with a Vite + React + TanStack + shadcn/ui frontend and a FastAPI + Postgres backend. Triggers on requests like "create a new app", "set up a project", "scaffold a full-stack app", "init a new project", or anything involving starting a fresh React/FastAPI application from scratch.

2026-07-132

cross-repo-discovery

bmsuisse/skills

Discover repos across the whole Azure DevOps org — not just the one you're sitting in — and figure out where a piece of functionality actually lives before assuming it doesn't exist locally. Generates ALL_REPOS.md, a map of every project/repo in the org, each repo's description, and whether it's already cloned locally (and where). Use this whenever the user asks about "other repos", "which repo has X", cross-repo/cross-service work, wants to find or clone a repo they don't have locally yet, or when you're stuck looking for code that isn't in the current repo and it might live elsewhere in the org. Trigger on things like "is there already a repo for this", "check across our other repos", "what repos do we have", "where's the shared X library", or "I don't think this exists yet, can you check devops".

2026-07-132

database-in-source

bmsuisse/skills

Conventions for versioning a PostgreSQL schema as plain `.sql` files inside a `database/` folder in the repo, instead of an ORM migration framework. Use when creating/organising a `database/` folder, adding a new table/view/function/type, or deciding where a migration script goes. Triggers on things like "add a new table to database/", "where do table definitions live", "database folder structure", "schema layer", "migration script", ".prod file", ".init.sql".

2026-07-102

postgres-best-practices

bmsuisse/skills

PostgreSQL coding standards for Python projects using psycopg (no ORM). Use this skill whenever the user is writing or reviewing code that queries PostgreSQL with psycopg, creates SQL files, maps query results to Python objects, or asks how to structure database access code. Triggers on things like "add a database query", "write a SQL query", "create a repository", "fetch from postgres", "insert into the database", "update the DB", "parameterized query", "pydantic model from DB row", "sql file", "dynamic SQL", or any mention of psycopg, psycopg2, asyncpg, or SQLAlchemy where the user seems open to a different approach. Also use when the user asks about connection pooling, transactions, cursor factories, or how to organise database code.

2026-07-102

postgres-test-setup

bmsuisse/skills

Set up and work with a local PostgreSQL test database in Docker for integration/e2e tests. Use this skill whenever the user wants to add, configure, troubleshoot, or run queries against a local test Postgres instance — even if they don't say "postgres" explicitly. Triggers on things like "set up a test database", "add postgres fixtures", "init test DB", "local postgres for tests", "add a column", "create a table", "change the schema", "run a SQL query on my test DB", "reset the database", "database is out of sync", "test data", or anything involving the local test Postgres database. Also use this skill when the user asks how to inspect the test DB, seed rows, or apply a migration to the local environment.

2026-07-102

name

bms

description

BMsuisse Master Skill

Detect sub-command and load the skill files listed for that mode. Apply all loaded skills in full. Always apply caveman communication rules.

Invocation	Skills to load
`/bms`	coding-guidelines-sql · coding-guidelines-python · coding-guidelines-typescript · fabricks-glossary
`/bms sql`	coding-guidelines-sql · sql-optimization · fabricks-glossary
`/bms python`	coding-guidelines-python
`/bms data`	data-modeling-dimensional · fabricks-glossary

Activation

Run the helper script to load all skill content for the active mode:
```
uv run skills/bms/scripts/load_skills.py [base|sql|python|data]
```
This outputs the combined content of all relevant SKILL.md files.
Apply all rules from the loaded output in full.
Respond with one confirmation line:
- /bms → "BMS active. Core guidelines loaded (SQL · Python · TypeScript)."
- /bms sql → "BMS SQL active."
- /bms python → "BMS Python active."
- /bms data → "BMS Data active."
Proceed immediately. No preamble.

For deep optimization invoke the specialized skills:

SQL performance → /databricks-sql-autotuner
Python performance → /python-autotuner

Caveman Mode (all sub-commands)

Respond terse like smart caveman. All technical substance stay. Only fluff die.

Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms.

Pattern: [thing] [action] [reason]. [next step].

Not: "Sure! I'd be happy to help you with that." Yes: "Bug in auth middleware. Fix:"

Code, commits, security warnings: write normal. Auto-clarity for irreversible actions.