team-shinchan:analytics
openbooklet.com/s/team-shinchananalyticsopenbooklet.com/s/team-shinchananalytics@1.0.0GET /api/v1/skills/team-shinchananalyticsUse when you need to analyze work tracker data for agent metrics or session stats.
Use when you need to analyze cascade impact of changing a component.
Use when you need to query, manage, or visualize the project-level ontology.
Use when you need deep analysis of code, bugs, performance, or architecture issues.
Use when you want autonomous completion from requirements to verification without intervention.
Use when you need backend development for APIs, databases, servers, or endpoints.
Use when you have a large-scale, multi-phase project requiring orchestrated execution.
Use when you need structured problem exploration before writing requirements.
Use when you need to view or manage workflow turn budgets and limits.
Use when you want multiple agents to debate and find optimal solutions.
Use when you need deep codebase exploration to find code, patterns, or references.
Use when you need to compare design mockups against implementation for UI fidelity.
Use when you need DevOps work like CI/CD, Docker, deployment, or pipelines.
Use when you need to diagnose the health of a team-shinchan project setup. Runs 7 deterministic checks (workflow state, hooks config, core scripts, runtime files, test directory) and reports PASS/WARN/FAIL per check with remediation hints.
Use when you need to view agent evaluation history or detect performance regressions.
Use when you need to delete specific outdated or incorrect memories.
Use when you need frontend development for UI components, React, CSS, or styling.
Use when you need guidance on Team-Shinchan agents, skills, or memory system.
Use when you need quick code implementation for features, bug fixes, or utilities.
Use when you need to view or manage learned memories and preferences.
Use when you want to orchestrate through the full integrated workflow stages.
Auto-indexed from seokan-jeong/team-shinchan
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.