원클릭으로 Manus에서 모든 스킬 실행

wiki-history-ingest

스타14

포크1

업데이트2026년 4월 28일 19:14

Unified wiki-history-ingest entrypoint for conversation/session sources. Use this when the user says "/wiki-history-ingest claude" or "/wiki-history-ingest codex", or asks to ingest agent history without naming the underlying skill. This router dispatches to the specialized history skill.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

saski

saski/augmentedcode-configuration

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Unified History Ingest Router

This is a thin router for history sources only. It does not replace wiki-ingest for documents.

Subcommands

If the user invokes /wiki-history-ingest <target> (or equivalent text command), dispatch directly:

Subcommand	Route To
`claude`	`claude-history-ingest`
`codex`	`codex-history-ingest`
`auto`	infer from context using rules below

Routing Rules

If the user explicitly says claude or codex, route directly.
If the user provides a path/source:
- ~/.claude or Claude memory/session JSONL artifacts -> claude-history-ingest
- ~/.codex or rollout/session index artifacts -> codex-history-ingest
If ambiguous, ask one short clarification:
- "Should I ingest claude or codex history?"
If the user asks for another history source, say that only claude and codex history ingesters are installed in this repository.

Execution Contract

After routing, execute the destination skill's workflow exactly.
Do not duplicate destination logic in this file.
Leave manifest/index/log update semantics to the destination skill.

UX Convention

Use wiki-ingest for documents/content sources
Use wiki-history-ingest for agent history sources

Examples:

/wiki-history-ingest claude
/wiki-history-ingest codex
$wiki-history-ingest claude (agents that use $skill invocation)

이 저장소의 다른 Skills

같은 저장소

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	wiki-history-ingest
description	Unified wiki-history-ingest entrypoint for conversation/session sources. Use this when the user says "/wiki-history-ingest claude" or "/wiki-history-ingest codex", or asks to ingest agent history without naming the underlying skill. This router dispatches to the specialized history skill.

Unified History Ingest Router

This is a thin router for history sources only. It does not replace wiki-ingest for documents.

Subcommands

If the user invokes /wiki-history-ingest <target> (or equivalent text command), dispatch directly:

Subcommand	Route To
`claude`	`claude-history-ingest`
`codex`	`codex-history-ingest`
`auto`	infer from context using rules below

Routing Rules

If the user explicitly says claude or codex, route directly.
If the user provides a path/source:
- ~/.claude or Claude memory/session JSONL artifacts -> claude-history-ingest
- ~/.codex or rollout/session index artifacts -> codex-history-ingest
If ambiguous, ask one short clarification:
- "Should I ingest claude or codex history?"
If the user asks for another history source, say that only claude and codex history ingesters are installed in this repository.

Execution Contract

After routing, execute the destination skill's workflow exactly.
Do not duplicate destination logic in this file.
Leave manifest/index/log update semantics to the destination skill.

UX Convention

Use wiki-ingest for documents/content sources
Use wiki-history-ingest for agent history sources

Examples:

/wiki-history-ingest claude
/wiki-history-ingest codex
$wiki-history-ingest claude (agents that use $skill invocation)