kimevans111/training-log-agent
A rule-based AI tool agent for deep learning training log analysis, metric diagnosis, tuning suggestions, plotting, and report generation.
A rule-based AI tool agent for deep learning training log analysis, metric diagnosis, tuning suggestions, plotting, and report generation.
npx skills add kimevans111/training-log-agentA rule-based AI tool agent for deep learning training log analysis, metric diagnosis, tuning suggestions, plotting, and report generation.
Open-source Claude Code skills marketplace — agent-army, claude-continuation, and more. Add once, install whichever you want. claude-skills.amjad1233.com
Custom skills for Microsoft Copilot Studio (utilizing Claude models) focused on AI use-case ideation and implementation in financial and M&A workflows
Structured competitive analysis with feature matrices, SWOT, positioning maps, and UX review. Covers research frameworks, pricing comparison, review mining, and visual deliverables. Use for: market research, competitive intelligence, investor decks, product strategy, sales enablement. Triggers: competitor analysis, competitive analysis, competitor teardown, market research, competitive intelligence, swot analysis, competitor comparison, market landscape, competitor review, competitive landscape, feature comparison, market positioning
Visual whiteboard collaboration for Copilot CLI. Creates an interactive whiteboard that opens in your browser — draw, sketch, add sticky notes, then share everything back with Copilot. Copilot sees your drawings and text, and responds with analysis, suggestions, and ideas.
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.
Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Engineer-audience, code identifiers welcome. Use after a debug session lands a fix, before closing the ticket. Trigger on /post-mortem, when the user says "write the post-mortem / postmortem / RCA / root cause analysis", "document this fix", "write up the root cause", "close out this bug with a writeup", or hands you a fixed-and-validated bug and asks for the writeup.