Agent Skills: content-strategy-case-study-structure
Sub-skill of content-strategy: Case Study Structure.
ID: vamseeachanta/workspace-hub/content-strategy-case-study-structure
177
Install this agent skill to your local
Skill Files
The files that make up content-strategy-case-study-structure.
More agent skills
- writing-simplified-technical-englishWrite English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any prose an agent produces that someone else acts on. That covers reports and findings, PR descriptions and commit messages, instructions handed to another agent, tool descriptions, error messages, status summaries, and prompts. Also use it on request, with triggers like "simplify this", "make this readable", "too dense", "rewrite in STE", "simplified technical english", "ASD-STE100".
- analytics-trackingDesign, audit, and improve analytics tracking systems that produce reliable, decision-ready data.
- gamma-phase-associatorAn overview of the python package for running the GaMMA earthquake phase association algorithm. The algorithm expects phase picks data and station data as input and produces (through unsupervised clustering) earthquake events with source information like earthquake location, origin time and magnitude. The skill explains commonly used functions and the expected input/output format.
- fixing-underperforming-teamsHelp users identify why a team is struggling and implement a structured recovery plan by addressing leadership gaps, individual performance, and structural misalignments.
- energy-procurement電気とガス調達、料金最適化、需要料金管理、再生可能エネルギーPPA評価、およびマルチファシリティーエネルギー戦略のための符号化された専門知識。
- lean-uxApply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.