Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

fic-research

Étoiles14

Forks1

Mis à jour7 mars 2026 à 21:17

Research and document the current codebase state without proposing changes. Use when the user asks to investigate existing behavior, architecture, or implementation details and capture findings.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

saski

saski/augmentedcode-configuration

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	fic-research
description	Research and document the current codebase state without proposing changes. Use when the user asks to investigate existing behavior, architecture, or implementation details and capture findings.

FIC Research

Act as a senior engineer documenting what exists today.

Rules

Describe current state only.
Do not propose fixes, refactors, or recommendations.
Include concrete evidence with file references.

Workflow

Read every file explicitly mentioned by the user.
Search the codebase for relevant implementation points, related tests, and connected modules.
Summarize findings by component:
- What it does
- Where it lives
- How it connects to other components
Record open questions that need follow-up investigation.

Output

When the repository has thoughts/, save to:

thoughts/shared/research/YYYY-MM-DD-topic.md

Recommended structure:

Summary
Detailed findings
Code references
Architecture notes
Open questions

Completion

End with:

Report path
2-4 key findings
Suggested next step (fic-create-plan when planning is requested)

Plus depuis ce dépôt

même dépôt

personal-knowledge-routing

saski/augmentedcode-configuration

Route durable personal context and reusable knowledge between augmentedcode-configuration and the personal knowledge vault. Use when the user asks to remember, persist, capture, retrieve, or organize personal knowledge; when deciding whether information belongs in rules, skills, portfolio, notes, maps, or inbox; or when using personal-knowledge-vault as a low-context reference layer.

2026-06-1714

github-host-alias

saski/augmentedcode-configuration

Use when running git clone, git remote add, git remote set-url, or suggesting GitHub SSH commands to ensure all GitHub access uses the saski SSH host alias.

2026-06-1714

building-data-apps

saski/augmentedcode-configuration

Build modern data apps, dashboards, and interactive reports using either React + Vite or Streamlit. Includes optional Gemini Data Analytics chat integration for an AI powered "chat with your data" experience. Relevant when any of the following conditions are true: 1. User explicitly requests to build a data dashboard, data application, or visualization UI, and the UI pulls data from a GCP database (defaulting to BigQuery unless otherwise specified). 2. You need to generate a frontend web application to interact with, query, and visualize data from GCP data sources. 3. User wants to build a "chat with your data" experience or integrate the Gemini Data Analytics chat API into a web interface. Do NOT use when any of the following conditions are true: 1. The request is for building backend-only services. 2. The request is for simple CLI scripts or command-line applications. 3. The web application is not data-centric or does not involve visualizing/querying data from GCP sources.

2026-06-0314

gcp-spark

saski/augmentedcode-configuration

Develops and executes Spark code on Dataproc Clusters and Serverless. Reads and writes data using BigLake Iceberg catalogs, BigQuery and Spanner. Debugs execution failures. Use when: - Writing Spark ETL pipelines on GCP. - Training or running inference with ML models with spark on GCP. - Managing Spark clusters, jobs, batches, and interactive sessions. Don't use when: - Writing generic Python scripts that don't use Spark. - Performing simple SQL queries that can be done directly in BigQuery.

2026-06-0314

lustra

saski/augmentedcode-configuration

Use when the user wants to clean up AI slop, harden a codebase, or run technical due diligence: review code for security flaws and vulnerable or wrongly-licensed dependencies, find and remove dead code, audit dependency health, run and triage linters, type checkers, test suites and formatters, evaluate design principles (SOLID and the cohesion/coupling equivalents for non-OO stacks), audit logging and observability, find performance smells, check documentation and CI health, scaffold baseline configs for the detected stack, do a structured code review, guide a one-major-at-a-time dependency migration, fix project structure, or produce one aggregated health report across all of these. Triggers on phrases like clean this up, find security issues, remove dead code, check dependencies, lint, typecheck, run the tests, format, review my code, check the design, check logging, is this slow, migrate a dependency, fix the project structure, set up the project, audit everything, due diligence, or this looks like AI slop

2026-06-0314

llm-council

saski/augmentedcode-configuration

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

2026-05-2714

name	fic-research
description	Research and document the current codebase state without proposing changes. Use when the user asks to investigate existing behavior, architecture, or implementation details and capture findings.

FIC Research

Act as a senior engineer documenting what exists today.

Rules

Describe current state only.
Do not propose fixes, refactors, or recommendations.
Include concrete evidence with file references.

Workflow

Read every file explicitly mentioned by the user.
Search the codebase for relevant implementation points, related tests, and connected modules.
Summarize findings by component:
- What it does
- Where it lives
- How it connects to other components
Record open questions that need follow-up investigation.

Output

When the repository has thoughts/, save to:

thoughts/shared/research/YYYY-MM-DD-topic.md

Recommended structure:

Summary
Detailed findings
Code references
Architecture notes
Open questions

Completion

End with:

Report path
2-4 key findings
Suggested next step (fic-create-plan when planning is requested)