brief-me
01tmusser/context-to-action-skills
Skill Claude CodeCodex
Catch the user up from messy workplace context and surface what needs attention.
34 tagged ai-productivity, measured the same way as everything else here.
Browse within: agentic-coding 8ai-coding-assistant 8ai-skills 8business-operations 7business-skills 7claude-cowork 7claude-desktop 7
tmusser/context-to-action-skills
Skill Claude CodeCodex
Catch the user up from messy workplace context and surface what needs attention.
tmusser/context-to-action-skills
Skill Claude CodeCodex
Turn meeting notes or transcripts into decisions, action items, owners, dates, blockers, and follow-ups.
tmusser/context-to-action-skills
Skill Claude CodeCodex
Use for dense or messy workplace source material - Slack threads, email chains, memos, transcripts, policy docs, vendor writeups, research notes, strategy notes, or customer escalations - before replying, deciding, escalating, or acting when context is long, ambiguous, stakeholder-sensitive, high-stakes…
TheCraigHewitt/cowork-starter-pack
Skill Claude CodeCodex
Part of cowork-starter-pack
Summarizes a long document, PDF, transcript, or report into a clear one-page brief with the key takeaways, notable quotes, and any action items. Use when the user asks to summarize, TLDR, give me the short version of, or digest a document. Works on files in the project folder or uploaded directly.
TheCraigHewitt/cowork-starter-pack
Skill Claude CodeCodex
Part of cowork-starter-pack
Processes a batch of emails — categorizes them, drafts responses where appropriate, and tells the user which ones need a human decision. Use when the user asks to triage the inbox, clear email, batch-process email, or prep email responses. Best run once or twice a day, not continuously.
TheCraigHewitt/cowork-starter-pack
Skill Claude CodeCodex
Part of cowork-starter-pack
Turns raw meeting notes or a rough recap into structured action items, a follow-up email draft, and a saved record for future reference. Use when the user says they just finished a meeting, wants to debrief a call, needs to send a follow-up, or wants to capture notes from a meeting. Pairs with meeting-prep — saves to…
beginnersinai/the-44-percent-rule
Skill Claude CodeCodex
Part of the-44-percent-rule
Automatically activates when users discuss AI adoption strategy, ask where to use AI in their business, want to find new AI use cases, or mention the 'mapping problem'. Provides the 10-function framework and examples of how other firms have reorganized around AI to help users discover unmapped opportunities.
beginnersinai/the-44-percent-rule
Skill Claude CodeCodex
Part of the-44-percent-rule
This skill should be used when the user types '/map', asks to 'run an AI mapping audit', 'scan my workspace for AI gaps', 'find where AI should be in my business', or wants a full workspace AI audit. Runs a comprehensive AI Mapping Audit based on Kim, Kim & Koning (2026) research.
beginnersinai/the-44-percent-rule
Skill Claude CodeCodex
Part of the-44-percent-rule
This skill should be used when the user types '/map-score', asks to 'score my AI opportunities', 'rank the gaps', 'prioritize the mapping results', or wants to score and rank AI mapping opportunities. Run this after using the map skill.
aishwaryaashok14/thefoundersfoyer-ai-product-skills
Skill Claude CodeCodex
Use when the user mentions AI workflows, automation, agents, AI productivity, "how do I use AI beyond ChatGPT," delegating to AI, replacing manual processes, building AI pipelines, prompt engineering, content automation, or scaling a small team with AI. Guides through audit, workflow design, and prompt iteration using…
Skill Claude CodeCodex
Turn any conversation into a queryable knowledge graph. Three-layer portable memory file: TRON (structured input+output capture with emotion, psychology, intent — every turn), Sparse6 (layered relational graph with community detection, hyperedges, confidence scores — every turn), GRAPHREPORT (god nodes + surprising…
Skill Claude CodeCodex
Two-tier project memory system. Maintains a global Claude memory snapshot of all ongoing projects AND a per-project STATUS.md file in each project folder that captures last-session state, next actions, blockers, and key locations — so context survives long absences. Operates in two modes. WRITE mode triggers when the…
Skill Claude CodeCodex
Clean stale, outdated, or redundant entries from Claude's stored memory. Use this skill when the user says things like "clean up memory", "prune memory", "memory is getting cluttered", "remove old entries", "consolidate memory", or "trim the memory map". Also trigger proactively when memory approaches its limits — 30…
Skill Claude CodeCodex
Load and summarise stored project memory at the start of a session, or whenever the user asks what Claude remembers about their work. Use this skill when the user says things like "what do you remember", "what's the context", "where did we leave off", "catch me up", "what's the current state", "show me the memory…
Skill Claude CodeCodex
Automatically detect and catalog recurring errors as AI pain points in need of skills. Activates when the same error is encountered twice in a session.
Skill Claude CodeCodex
Maintain a living, self-updating understanding of a repo through a decomposable document surface. Use when you want project coherence that accrues over time via one-question-at-a-time investigation rather than one-shot snapshots. Complements bootstrap-project (which produces a snapshot) by providing ongoing continuity.
Skill Claude CodeCodex
Automatically capture, update, and manage development pain points. Use when user mentions friction, blockers, workarounds, or wants to track development obstacles. Auto-invokes during weekly reviews.
Skill Claude CodeCodex
Part of goalify
Hand Claude a huge task. Come back to proof it's done — not a promise that it is. goalify writes the brief (a file with the instructions the run works from) and the condition (a short string you paste into /goal), because /goal takes a condition string, never a file path. Use when the user says "goalify", "goalify…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: