ワンクリックでManusで任意のスキルを実行

insight-install

スター0

フォーク0

更新日2026年4月25日 01:42

Use this skill when a Claude instance is bootstrapping a new repository or onboarding a project that is not yet wired into the team insights system. Trigger phrases include "install insights into this repo", "wire insights-share here", "/insight-install", "wire this repo so teammates inherit insights". The skill idempotently appends a force-install block to the project CLAUDE.md (append-only) and verifies hook registration so any future Claude instance entering this repo is guided to install the plugin.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

liush2yuxjtu

liush2yuxjtu/insights-share

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

insight-install

You are the onboarding side of the team insights system. Your job is to make a fresh repo enforce that every future Claude collaborator picks up this plugin.

When to invoke yourself

The user says "install insights here" / "wire this repo so teammates inherit insights" / /insight-install.
You enter a repo whose CLAUDE.md does not contain the marker .
A teammate asks you to standardize a new project for the team's knowledge flow.

What you must do

Resolve target root: $ARGUMENTS if set, else current working directory.
Verify a CLAUDE.md already exists at that root. Do not create one — that is the team's decision, not yours. If missing, tell the user and stop.

Run the append script directly (same code the SessionStart hook uses):

echo "{\"cwd\":\"<absolute-project-root>\"}" \
  | bash "${CLAUDE_PLUGIN_ROOT}/scripts/append-claude-md.sh"

Re-read CLAUDE.md and confirm the marker line  is present exactly once.
Report:
- what was appended (in a fenced block),
- the marker line number,
- that future Claude instances entering this repo will now see the install hint on their SessionStart.

Guarantees

Append-only. Never delete, rewrite, or reorder existing content in CLAUDE.md.
Idempotent. If the marker is already present, do nothing and say so.
No silent surprise. Always show the user the diff before saying "done".

このリポジトリの他の Skills

同じリポジトリ

insight-flush

liush2yuxjtu/insights-share

Use this skill when the user wants to force-finalize the in-flight session buffer immediately, instead of waiting for the 30-min idle threshold. Triggered by "/insight-flush", "flush insights", "push my insight buffer now", "publish lessons now", "force-sync the mirror". Reads the local buffer, runs the two-layer PII filter, and pushes any surviving lessons to the mirror repo.

2026-04-250

insight-rate

liush2yuxjtu/insights-share

Use this skill when the user (or another Claude instance) wants to rate a previously injected insight as good / bad / irrelevant for the current task. Triggered by "/insight-rate", "rate this insight", "this lesson saved me time", "this lesson was wrong", "thumbs up the insight", or similar phrasings. Writes a single rating record to the per-repo ratings.jsonl. Used at Gate 1 to compute "≥1 cross-engineer relevant retrieval / week" and detect drift in topic-tag inference.

2026-04-250

insight-help

liush2yuxjtu/insights-share

Use this skill when the user has just installed the insights-share plugin and asks any onboarding question — "what next", "where is the README", "how do I use this plugin", "/insight-help", "show me the insights-share quickstart", "what does this plugin do for me". The skill prints a compact onboarding card pointing to the README on disk, the four slash commands, statusline wiring, and the optional self-host stub server.

2026-04-250

insight-add

liush2yuxjtu/insights-share

Use this skill when a Claude instance has just hit, fixed, or learned about a non-obvious trap that another teammate (or another Claude instance) would benefit from knowing. Trigger phrases include "save this as a team insight", "add insight", "log a lesson", "/insight-add", "we should record this so others don't repeat it". The skill captures one structured insight card and POSTs it to the team insights server.

2026-04-250

insight-search

liush2yuxjtu/insights-share

Use this skill when a Claude instance wants to manually look up team insights before acting on a non-trivial task — e.g. before changing build configuration, touching auth, writing a migration, or wiring a hook. Trigger phrases include "search insights", "any team lesson on X", "/insight-search", "have we hit this before". The skill performs a keyword search against the team insights server and renders the top hits as a compact briefing.

2026-04-250

insight-server

liush2yuxjtu/insights-share

Use this skill when a Claude instance needs to start, stop, ping, or run the nightly automation cycle of the self-host insights server. Trigger phrases include "start insights server", "ping the insights server", "run nightly insights sync", "/insight-server start|stop|ping|nightly", "is the team insights backend up". The skill is a thin operator over the self-host server stub documented in references/self-host.md; the production backend is intentionally deferred.

2026-04-250

name	insight-install
description	Use this skill when a Claude instance is bootstrapping a new repository or onboarding a project that is not yet wired into the team insights system. Trigger phrases include "install insights into this repo", "wire insights-share here", "/insight-install", "wire this repo so teammates inherit insights". The skill idempotently appends a force-install block to the project CLAUDE.md (append-only) and verifies hook registration so any future Claude instance entering this repo is guided to install the plugin.
argument-hint	[optional path to project root, defaults to cwd]
allowed-tools	Bash, Read

insight-install

You are the onboarding side of the team insights system. Your job is to make a fresh repo enforce that every future Claude collaborator picks up this plugin.

When to invoke yourself

The user says "install insights here" / "wire this repo so teammates inherit insights" / /insight-install.
You enter a repo whose CLAUDE.md does not contain the marker .
A teammate asks you to standardize a new project for the team's knowledge flow.

What you must do

Resolve target root: $ARGUMENTS if set, else current working directory.
Verify a CLAUDE.md already exists at that root. Do not create one — that is the team's decision, not yours. If missing, tell the user and stop.

Run the append script directly (same code the SessionStart hook uses):

echo "{\"cwd\":\"<absolute-project-root>\"}" \
  | bash "${CLAUDE_PLUGIN_ROOT}/scripts/append-claude-md.sh"

Re-read CLAUDE.md and confirm the marker line  is present exactly once.
Report:
- what was appended (in a fenced block),
- the marker line number,
- that future Claude instances entering this repo will now see the install hint on their SessionStart.

Guarantees

Append-only. Never delete, rewrite, or reorder existing content in CLAUDE.md.
Idempotent. If the marker is already present, do nothing and say so.
No silent surprise. Always show the user the diff before saying "done".