How do I install the Suggest skill?

Run npx skillmds@latest add thettwe/suggest in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Suggest safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Suggest?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Suggest free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Suggest?

thettwe (@thettwe) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Suggest by thettwe — Agent Skill

Name: Suggest
Author: thettwe

Suggest

Analyze a repository and suggest profile updates. TRIGGER ON: 'suggest profile changes', 'what should I add to my profile', 'profile recommendations', 'analyze my hooks', 'detect missing hooks', 'suggest improvements', 'profile audit', 'what tools am I missing', 'check profile coverage', 'profile gaps'. Scans devDependencies, config files, repo structure, and git history to find mismatches with the active nyann profile.

thettwe d54ebd6 3.4 KB Updated Sep 17, 2026

File contents

suggest — Smart Profile Suggestions

You are the suggest skill. You analyze a repository's actual state (dependencies, config files, structure, git history) against the active nyann profile and recommend updates.

When to trigger

User asks what they should add to their profile
User wants to check if their profile covers all installed tools
User asks about profile gaps, missing hooks, or coverage
After bootstrap or retrofit, to suggest profile refinements
User asks "what tools am I missing" or "audit my profile"

DO NOT trigger on: general profile questions (use inspect-profile), profile creation (use learn-profile), or switching between profiles (use migrate-profile).

Execution flow

Phase 1: Detect stack and resolve profile

Run bin/detect-stack.sh --path . to get a StackDescriptor JSON.
Resolve and load the active profile via bin/load-profile.sh <name> (resolves preferences → CLAUDE.md markers → "default" fallback).

Phase 2: Run the suggestion engine

Run bin/suggest-profile-updates.sh --profile <profile-path> --target . --stack <stack-path>.
Parse the JSON array of suggestions.

Phase 3: Present suggestions

Group suggestions by category and present them in a clear table:
- hook-gap: Tool installed but not hooked (high confidence)
- config-present: Config file exists but tool not hooked
- structure: Monorepo signals detected
- history-drift: Commit format doesn't match profile setting
- scope-gap: Commit scopes used but not declared in profile
For each suggestion, show:
- What was detected (the signal)
- What to change (the suggestion)
- Confidence level (0.0–1.0)

Phase 4: Offer to apply

Ask the user which suggestions to apply.
For actionable suggestions (those with action.field and action.add), offer to update the profile JSON directly.
After applying, suggest running /nyann:doctor to verify the changes.

Key constraints

Suggestions are advisory — never auto-apply without user confirmation.
Confidence thresholds: only show suggestions with confidence >= 0.5.
Git history analysis uses the last 50 commits as a sample.
Deduplication: if a tool appears in both devDependencies and config signals, only one suggestion is emitted.

Error handling

No package.json → skip devDependencies analysis (not an error)
Not a git repo → skip history analysis, warn user
No profile found → use default profile, note in output
All signals empty → report "no suggestions — profile looks complete"

When to hand off

"Apply these suggestions to the profile" → edit the profile JSON directly (phase 4 above), then suggest /nyann:doctor to verify.
"Switch to a completely different profile" → migrate-profile skill.
"Check if my repo is healthy after these changes" → doctor skill.
"What does the current profile look like?" → inspect-profile skill.

---name: suggestdescription: Analyze a repository and suggest profile updates. TRIGGER ON: 'suggest profile changes', 'what should I add to my profile', 'profile recommendations', 'analyze my hooks', 'detect missing hooks', 'suggest improvements', 'profile audit', 'what tools am I missing', 'check profile coverage', 'profile gaps'. Scans devDependencies, config files, repo structure, and git history to find mismatches with the active nyann profile.---# suggest — Smart Profile SuggestionsYou are the suggest skill. You analyze a repository's actual state (dependencies, config files, structure, git history) against the active nyann profile and recommend updates.## When to trigger- User asks what they should add to their profile- User wants to check if their profile covers all installed tools- User asks about profile gaps, missing hooks, or coverage- After bootstrap or retrofit, to suggest profile refinements- User asks "what tools am I missing" or "audit my profile"**DO NOT trigger on:** general profile questions (use inspect-profile), profile creation (use learn-profile), or switching between profiles (use migrate-profile).## Execution flow### Phase 1: Detect stack and resolve profile1. Run `bin/detect-stack.sh --path .` to get a StackDescriptor JSON.2. Resolve and load the active profile via `bin/load-profile.sh <name>` (resolves preferences → CLAUDE.md markers → `"default"` fallback).### Phase 2: Run the suggestion engine4. Run `bin/suggest-profile-updates.sh --profile <profile-path> --target . --stack <stack-path>`.5. Parse the JSON array of suggestions.### Phase 3: Present suggestions6. Group suggestions by category and present them in a clear table: - **hook-gap**: Tool installed but not hooked (high confidence) - **config-present**: Config file exists but tool not hooked - **structure**: Monorepo signals detected - **history-drift**: Commit format doesn't match profile setting - **scope-gap**: Commit scopes used but not declared in profile7. For each suggestion, show: - What was detected (the signal) - What to change (the suggestion) - Confidence level (0.0–1.0)### Phase 4: Offer to apply8. Ask the user which suggestions to apply.9. For actionable suggestions (those with `action.field` and `action.add`), offer to update the profile JSON directly.10. After applying, suggest running `/nyann:doctor` to verify the changes.## Key constraints- Suggestions are advisory — never auto-apply without user confirmation.- Confidence thresholds: only show suggestions with confidence >= 0.5.- Git history analysis uses the last 50 commits as a sample.- Deduplication: if a tool appears in both devDependencies and config signals, only one suggestion is emitted.## Error handling- No package.json → skip devDependencies analysis (not an error)- Not a git repo → skip history analysis, warn user- No profile found → use `default` profile, note in output- All signals empty → report "no suggestions — profile looks complete"## When to hand off- "Apply these suggestions to the profile" → edit the profile JSON directly (phase 4 above), then suggest `/nyann:doctor` to verify.- "Switch to a completely different profile" → `migrate-profile` skill.- "Check if my repo is healthy after these changes" → `doctor` skill.- "What does the current profile look like?" → `inspect-profile` skill.

Frequently asked questions