The Open edX Instructor Dashboard
structured outputs for llms
Pydantic/Instructor-style LLM output validation with retry loops and grammar enforcement
Dual-AI orchestration CLI that coordinates Instructor and Worker Claude instances
No description provided.
OpenTelemetry instrumentation for Instructor
🛠 Tools to help presenters build engaging instructor led training for the timesplitter
<p align="center">
Werkout-server is the place where the instructor and the partners meet to perform Werkout sessions and communicate with each other
A tool that allows live syncing from an instructor's code project. Must be paired with code-live-instructor.
Streaming-first structured data extraction from LLMs with real-time updates
🤖 Everything you need to start creating outstanding instructor led courses for the timesplitter
I have made a resume, by following the instructions by the instructor.
Yoga class and instructor module using TypeScript, Mongoose, and MongoDB
## LoginForm and getClient
A comprehensive web application for managing student, course, instructor, and employee data within a Students Affairs department. Features CRUD operations, pagination, search, and sorting capabilities.
structured outputs for llms
This visualization dashboard unites several visualizations and provides interactions between them. Visualization filters allow the instructor to filter the training events and their format.
A JSX-based templating engine for generating structured prompts with TypeScript support
This is the package which is requested by our respected instructor
Vagner Silva package
A tool that allows live syncing from an instructor's code project to a student's computer. Must be paired with code-live-student.
This package is designed to provide synchronous communication between the associated users. The widget component is built and exported as a web-component so it is framework/library agnostic
As an instructor, a user can see the ongoing course of the training runs and further filter information on demand. The tool gives a full picture of the trainee’s walkthrough. Upon filtering in the preceding sections, selected trainees are displayed here.
Coming soon...
Type-safe structured output extraction from LLMs. The Rust instructor.
Get structured, validated data out of LLMs as native Rust structs and enums. Derive a type and rstructor generates the JSON Schema, prompts the model, parses the reply, and retries on validation errors — across OpenAI, Anthropic Claude, Google Gemini, and xAI Grok. The Rust answer to Python's Pydantic + Instructor.
instructor-ai is a simple crate that allows for users to do validated structured outputs
collection of common solana instructions
LTI Tool related functionality for Axum
Derive macros for rstructor: generate JSON Schema from Rust structs and enums to extract structured, validated outputs from LLMs (the Instructor pattern for Rust).
Rust CLI that generates GitHub Classroom autograder workflows for Rust assignments.
instruct-macros are a collection of simple macros that we're using in Instructor-AI to generate json schema from Serde Objects
Instructor Macro Types are a collection of simple types that we export to work with the instruct-macros crate
Parsers and transformers for non-standard text markup in Merriam-Webster's Collegiate Dictionary API
AgentSkills parser, index, and runtime injection helpers for ADK-Rust
Input structure base object for capturing and validating input with a nice DSL
Explore the power of LLM structured extraction in Ruby with the Instructor gem.
Dive into the world of Python-based structured extraction, empowered by OpenAI's cutting-edge function calling API. Instructor stands out for its simplicity, transparency, and user-centric design. Whether you're a seasoned developer or just starting out, you'll find Instructor's approach intuitive and its results insightful.
Includes often used scripts to help Flatiron School instructors
tool for Flatiron School instructors to group students for projects
tool for Flatiron School instructors to group students for projects
tool for Flatiron School instructors to group students for projects
Manage the development lifecycle of Puppet courseware. This tool is not required for presenting the material or for contributing minor updates. This tool is not intended for general usage. If you are not a Puppet instructor or an authorized training partner, this gem will have little interest for you.
The Programming Exercise Markup Language (PEML) is intended to be a simple, easy format for CS and IT instructors of all kinds (college, community college, high school, whatever) to describe programming assignments and activities. We want it to be so easy (and obvious) to use that instructors won't see it as a technological or notational barrier to expressing their assignments. We intend for this format to be something that authors of automated grading tools can adopt, so they can provide a very easy, low-energy onboarding path for existing instructors to get programming activities into such tools. As a result, this notation leans heavily on supporting authors and streamlining common cases, even if this may require more work on the part of tool developers--the goal is to make it super easy for authors of programming activities, not to fit into a specific auto-grader or simplify tasks for tool writers. For more details, see the PEML website.
<!-- TABLE OF CONTENTS --> <details open="open"> <summary>Table of Contents</summary> <ol> <li> <a href="#about-the-project">About The Project</a> <ul> <li><a href="#built-with">Built With</a></li> </ul> </li> <li> <a href="#getting-started">Getting Started</a> <ul> <li><a href="#prerequisites">Prerequisites</a></li> <li><a href="#installation">Installation</a></li> </ul> </li> <li><a href="#usage">Usage</a></li> <li><a href="#roadmap">Roadmap</a></li> <li><a href="#contributing">Contributing</a></li> <li><a href="#license">License</a></li> <li><a href="#contact">Contact</a></li> <li><a href="#acknowledgements">Acknowledgements</a></li> </ol> </details> <!-- ABOUT THE PROJECT --> ## About The Project [![Product Name Screen Shot][Screenshot of gameplay and test list]](https://www.dropbox.com/s/mu1rrbx2mqowjkn/studio-game.png?dl=0) This game is a project built following the [Pragmatic Studio Ruby Course](https://online.pragmaticstudio.com/courses/ruby/). I absolutely adored going through this course, because it was unlike other courses in that the main focus wasn't syntax, but how to build a principle-driven, object-oriented program that contains many of the skills we'd need to build real-world projects. The instructors purposefully created exercises to let us build a program using the skills they demonstrated by building a different program. This wasn't a copy and paste kind of course. This game was actually my second run-through, where I test-drove everything from the start based on the objectives only. Skills I valued developing further with this project: - Test-driven development (50+ tests). - Using inheritance to model "is-a" relationships. For example, a clumsy player *is a* kind of player. - Using mixins (modules) to reuse behaviours that are common between classes, but should not be modeled with an inheritance relationship. A good tip was to look for 'able' behaviors in a class to extract, like 'playable', 'printable', 'taxable' etc. - Using a file block which lets you add in class usage examples that are only run when you run the class file specifically. - Overriding default methods (like sort, and renaming things so that they keep a specific format) Things I struggled with: - Testing behaviour that uses blocks. I had a lightbulb moment when I realised I should test the behaviour performed inside the block on a single item. Testing the output of an entire block is like testing Ruby syntax works. Alternatively, test the before and after state of something that changes as a result of using a block. Cooool. - Puts. It felt wrong to use puts to show the output in the console. I'd like to learn how to seperate the view logic for a command-line project later. Things I did to make it my own: - Wrote a lot more tests for my second run-through. - Noticed and extracted further 'able' behaviours into modules (like printing stats, formatting output and handling csv files). ### Built With * [Ruby (language)](https://www.ruby-lang.org/en/) * [RSpec (framework)](https://rspec.info/) * [Vim (text-editor)](https://www.vim.org/) <!-- GETTING STARTED --> ## Getting Started To get a local copy up and running follow these steps: ### Prerequisites This is an example of how to list things you need to use the software and how to install them. * gem ```sh npm install npm@latest -g ``` ### Installation 1. Install the gem ```sh gem install studio_game_2021 ``` <!-- USAGE EXAMPLES --> ## Usage To play a game from the command-line, open a new command project and run the command-line script like so: ```sh studio_game ``` Or, if you'd like to use the game as a library, here's an example of how to use it in `irb`. You can also check the bottom of each class or module file for further usage instructions ``` >> require 'studio_game/game' => true >> game = StudioGame::Game.new("Knuckleheads") => #<StudioGame::Game:0x007fdea10252d8 @title="Knuckleheads", @players=[]> >> player = StudioGame::Player.new("Moe", 90) => I'm Moe with health = 90, points = 0, and score = 90. >> game.add_player(player) => [I'm Moe with health = 90, points = 0, and score = 90.] >> game.play(1) ``` <!-- ROADMAP --> ## Roadmap I plan to customize this game further now that I have a solid foundation to explore from. It'll be fun to let the players interact with each other more, like swapping treasures, and maybe add some kind of board game with it's own features. That's my next focus. ## Contributing Feel free to fork this project and play around with it. Open to feedback-related pr requests. <!-- LICENSE --> ## License Distributed under the MIT License. See `LICENSE` for more information. <!-- CONTACT --> ## Contact Becca - [@becca9941](https://twitter.com/Becca9941) - becca@essentialistdev.com Project Link: [https://gitlab.com/EssentialistDev/studio-game](https://gitlab.com/EssentialistDev/studio-game) <!-- ACKNOWLEDGEMENTS --> ## Acknowledgements - [Pragmatic Studio](https://online.pragmaticstudio.com/courses/ruby/) for empowering me with awesome new development skills. - [Best-README-Template](https://github.com/Becca9941/Best-README-Template) for helping me write a README for this project.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.