hubeiqiao/tim-project-skills/g1-slide-deck-guide

Claude Code and agent skill by hubeiqiao/tim-project-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Use when creating, reviewing, or revising a Carleton University Technology Innovation Management (TIM) Gate 1 slide deck - provides slide structure, content expectations, formatting guidance, and the six official G1 guidelines.

Install

npx vskill@latest install hubeiqiao/tim-project-skills/g1-slide-deck-guide

SKILL.md

TIM Gate 1 (G1) Slide Deck Guide

What This Skill Helps With

Use this skill when you are building or reviewing a Carleton University Technology Innovation Management (TIM) Gate 1 presentation and need help with slide order, required content, formatting, pathway alignment, or presentation expectations.

Ask for this skill with prompts like

  • Use $g1-slide-deck-guide to review whether my Gate 1 deck has the right slide order.
  • Use $g1-slide-deck-guide to turn this TIM project outline into a G1 slide plan.
  • Use $g1-slide-deck-guide to check whether my deliverables and novelty slides match the guideline.
  • Use $g1-slide-deck-guide to compare my draft deck against the expected G1 structure.

Source and Scope

This skill summarizes TIM Gate 1 guideline materials, the official slide template, and example decks. Use it as a working guide for G1 slide support, then confirm any final submission details against the latest supervisor or program instructions.

Source documents synthesized:

  1. Guidelines/G1 Slide Deck/Guide for G1 Slide Decks.txt - 6 official guidelines + G1 objectives
  2. Guidelines/G1 Slide Deck/TIM_gate1_project_template_2025_Feb 14.ppt - official template
  3. Guidelines/G1 Slide Deck/BRECK AGYEKUM. G1 deck.Aug 26.pdf - example (MEng, AI Logistics, 32 pages)
  4. Guidelines/G1 Slide Deck/Veronica Ihem G1 deck Aug 26.pdf - example (MDTE, Agrifood Trade, 36 pages)

1. G1 Presentation Objectives

The Gate 1 project presentation emphasizes:

  • Research method, data acquisition, and data analysis
  • Preliminary results achieved to date of presentation
  • How the TIM project meets pathway-specific requirements
  • Reasons the project is novel and the expected project contribution to the client
G1 Deliverables
  • A Gate 1 slide deck using the TIM project template - due the day before the G1 presentations
  • A ten-minute presentation of the Gate 1 slide deck to the Supervisor and the audience (e.g., client, other TIM faculty)
  • Answers to questions. On average the Q&A session lasts 15 minutes

2. Slide-by-Slide Structure

The following structure is derived from the official template and validated against both example decks. Slide numbers are approximate; some slides may span multiple pages depending on content volume.

Slide 1: Title Slide
  • Content:
  • Project title (bold, large font)
  • Author name (regular or italic)
  • "Gate 1 ([Pathway]) Project presentation" in italics (e.g., "Gate 1 (MEng.) Project presentation" or "Gate 1 (MDTE) project presentation")
  • "Technology Innovation Management"
  • Date of presentation
  • Visual elements: Carleton University logo (top right), red/blue header bar below logo, brown footer bar at bottom
  • Footer: May or may not appear on the title slide (Breck omits footer on Slide 1; Veronica includes it)
Slide 2: Objectives and Deliverables
  • Objective: A single paragraph stating the project objective. Must be SMART (Specific, Measurable, Achievable, Relevant, Time-bound) and achievable within 13 weeks.
  • Deliverables: A numbered list of deliverables (typically 2-7 items). Each deliverable should be a concrete output.
Slide 3: Relevance to the Client Company
  • Required subsections:
  • Client: Name and brief description of the client organization
  • Client Contact: (optional but recommended) Name(s) of client contacts
  • Evidence of Interest: Why the client needs this research; specific challenges they face
  • Potential Value to Client: Bulleted list of benefits the research provides
  • Relationship to Client: (optional) How the project was initiated
Slide 4: Problem and Gap
  • Client problem: A clearly structured problem statement that is solvable within 13 weeks and directly addressed by the research. Must include three elements:
  • Client: Who benefits from the research
  • Subject: The specific challenge the research addresses
  • Measurement: How the challenge's impact is measured
  • What is Known: Bullet points with citations describing the current state of knowledge
  • What is Not Known: Bullet points phrased as questions, each explicitly mapped to one or more deliverable numbers (e.g., "What is known about X? (Deliverable 1)")
Slide 5: Literature Review
  • Format: Table with three columns:
  • Stream - the literature theme/topic
  • Key highlights of the stream - bullet points summarizing key findings
  • Citations to key sources - author-date citations
  • Typically 4-7 streams are presented
  • Each stream should connect to a deliverable or client need
Slide 5 (alternate position): Project Novelty
  • Note: Some presenters (e.g., Veronica) place a "Project Novelty" slide before the Literature Review (as Slide 5), pushing Literature Review to Slide 6. This is an acceptable variation. Breck places Novelty near the end (after results).
Slide 6: Research Method
  • Introductory sentence describing the overall method approach
  • Table with three columns:
  • Step - numbered step (typically 5-10 steps)
  • Activity - description of what was done at each step
  • Outcome - what was produced at each step
  • If the method table is long, it may span two slides (e.g., "Research Method 1/2" and "Research Method 2/2")
Slide 7: Data Acquisition
  • Content varies by project but typically includes:
  • Type of data collected
  • Variables collected / measured
  • Data sources and retrieval methods
  • May use a table format (columns: Data type, Source of data, Acquisition method)
  • May use bullet-point format (Type of Data, Variables Collected, Data Sources & Retrieval)
Slide 8: Data Acquisition Process / Data Analysis
  • This slide (or pair of slides) describes:
  • How data was collected (search strategies, screening, validation)
  • How data was analyzed (thematic coding, statistical methods, tools used)
  • May include workflow diagrams or step-by-step descriptions
  • If content is substantial, Data Acquisition and Data Analysis may each get their own slide
Slides 9+: Results / Deliverable Slides
  • One section per deliverable, each with its own heading: "Deliverable 1. [Name]", "Deliverable 2. [Name]", etc.
  • Each deliverable section may span 1-4 slides depending on complexity
  • Include tables, charts, diagrams, flowcharts, and visual summaries as appropriate
  • Results must directly correspond to the deliverables listed on Slide 2
  • Content should show preliminary results achieved to the date of presentation
Discussion of Results
  • Summarize key findings across all deliverables
  • Highlight the most important insights
  • Connect findings back to the client problem (Slide 4)
  • Bullet-point format is typical
Pathway Requirements Slide
  • Title: "Why your project meets your pathway requirements"
  • Explain how the project satisfies the specific pathway requirements (MEng, MDTE, etc.)
  • Typically 4-5 bullet points
  • Content should reference the pathway's emphasis (e.g., applied research, engineering analysis, interdisciplinary integration, commercialization focus, professional communication for MEng)
Novelty Slide
  • Title: "Novelty of The Project" or "Project Novelty"
  • Explain what makes the project new or unique
  • Typically 4-5 bullet points covering:
  • Underexplored area or novel application
  • Tailored approach for the specific context
  • Practical/actionable outputs
  • Reusable method or framework
  • Placement: Can appear early (after Problem and Gap, before Literature Review) or late (after results, before Limitations). Both placements are observed in examples.
Limitations Slide
  • Bullet-point list of project limitations (typically 4-6 items)
  • Common limitations: limited data, time constraints, scope restrictions, transferability concerns, cost/integration uncertainty, data quality risks
Suggestions for Future Research / Recommendations
  • Bullet-point list of future research directions or recommendations (typically 4-6 items)
  • Should address how future researchers can overcome the identified limitations
Conclusion (optional, observed in Veronica's deck)
  • Summary of key accomplishments and results
  • May include a "Results Now, Mechanism to Scale" framing
References
  • Numbered reference list
  • May span multiple slides if the reference list is long (1-6 slides observed)
  • Follow a consistent citation style throughout

3. The Six Official Guidelines

These are the six guidelines from the official "Guide for G1 Slide Decks":

Guideline 1: Define the Client Problem (Slide 4)

Structure your problem statement clearly, ensuring it is solvable within 13 weeks and directly addressed by your research. Include:

  • The Client: Identify who benefits from the research
  • The Subject: Describe the specific challenge faced
  • The Measurement: Detail how the impact is measured by the client and stakeholders
Guideline 2: Highlight Research Benefits

Explicitly detail how your research will benefit the client and stakeholders.

Guideline 3: Connect "Not Known" to "Literature Review" and "Deliverables"
  • Address unknown aspects (Slide 4) with findings from your literature review (Slide 5)
  • Align deliverables (Slide 2) with these unknowns to provide solutions
Guideline 4: Clarify Your Objective (Slide 2)

Your objective should be SMART (Specific, Measurable, Achievable, Relevant, Time-bound) and achievable within 13 weeks.

Guideline 5: Enhance Your Slides
  • Aim for clear, precise communication and a professional appearance to positively influence audience perception
  • Eliminate errors in spelling, grammar, and formatting
  • Adhere to the "Guidelines to Write a TIM Project Report" for content consistency
  • Favor succinct text over lengthy descriptions
Guideline 6: Align Deliverables (Slide 2) with Results (After Slide 8)

Ensure your deliverables (Slide 2) directly match the results presented after Slide 8. Avoid proposing deliverables A, B, C, and then presenting unrelated results W, X, Y, Z.


4. Footer and Formatting

Footer Format

The footer appears on a brown/dark bar at the bottom of each slide. It contains three elements:

  • Left: Author's email address (italic, e.g., onwonaagyekum@cmail.carleton.ca or veronicaamadiihem@gmail.com)
  • Center: Date (e.g., "July 29th, 2025" or "August 26th 2025")
  • Right: Slide number (italic, e.g., "Slide 2", "Slide 3")
Header Format
  • Carleton University logo in the top-right corner of every slide
  • A thin red/blue horizontal line below the logo area, spanning the slide width
Slide Title Format
  • Bold, large font
  • Left-aligned
  • No period at the end of slide titles
General Formatting Rules
  • Use the official TIM project template (TIM_gate1_project_template_2025)
  • Professional appearance with consistent fonts and spacing
  • Tables should have clear column headers and consistent formatting
  • Charts and figures should be properly labeled
  • Succinct text preferred over lengthy descriptions
  • Eliminate spelling, grammar, and formatting errors
Footer Numbering Notes
  • Footer slide numbers should increment sequentially (Slide 1, Slide 2, Slide 3...)
  • The title slide may be Slide 1 (with or without footer)
  • Footer numbering should be consistent throughout the deck
  • Known issue in examples: Some decks have numbering inconsistencies in later slides (e.g., multiple slides labeled "Slide 24"). Avoid this.

5. Critical Alignment Rules

These alignment requirements are essential for a well-structured G1 deck:

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
1
7-day trend score
3

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/hubeiqiao/tim-project-skills/g1-slide-deck-guide/badge)](https://verified-skill.com/skills/hubeiqiao/tim-project-skills/g1-slide-deck-guide)

Something wrong with this skill or its page? Tell us.