← Back to Skills Marketplace
lystea11

Edsby Grades Board

by Lystea11 · GitHub ↗ · v1.0.1
cross-platform ⚠ suspicious
984
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install edsbygrades
Description
Fetches Edsby student data to generate grade reports, provide bi-weekly summaries with tips, and sync assignments to Google Calendar.
README (SKILL.md)

Edsby Student Integration Skill\r

\r Author: Lysandre Stone-Bourgeois\r Version: 1.0.0\r Description: Integrates with Edsby via browser relay to fetch classes/grades/assignments, generate reports/summaries, and sync due dates to Google Calendar. Includes scheduled checks.\r Tools: \r

  • edsby_fetch_data: Fetches raw data from Edsby.\r
  • edsby_generate_report: Creates personalized report.\r
  • edsby_sync_assignments: Syncs due dates to Google Calendar.\r
  • edsby_generate_summary_improvements: Bi-weekly grade summary with tips.\r
  • edsby_daily_check: Daily assignment check and sync.\r \r Dependencies: playwright, googleapis\r Config: EDSBY_HOST, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI, GOOGLE_CALENDAR_ID, BROWSER_CONTEXT_PATH\r Security: Uses persistent browser sessions; handle creds securely.
Usage Guidance
Key things to consider before installing: - The registry metadata does not list the env vars the code needs. Ask the publisher to explicitly declare: EDSBY_HOST, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI, GOOGLE_CALENDAR_ID, and BROWSER_CONTEXT_PATH. - The skill stores OAuth tokens in a local file named google-tokens.json and uses a persistent browser context directory. Confirm where those files will live, and prefer a dedicated, isolated path (not your regular browser profile or a directory with other sensitive data). - Playwright will download browser binaries during install — expect extra disk usage and network activity. Consider running this skill in an isolated environment (container or VM). - If you plan to grant Google OAuth credentials, rotate them if you uninstall the skill. Inspect the token file contents and store tokens in a secure secrets store if possible rather than plaintext files. - If you cannot confirm the publisher or fix the metadata omissions, treat this as higher-risk and avoid giving real credentials or persistent browser profiles to the skill. Request the author to fix the registry entries and to document secure token handling and installation steps.
Capability Analysis
Type: OpenClaw Skill Name: edsbygrades Version: 1.0.1 The skill bundle is designed to integrate with Edsby and Google Calendar, fetching student data and syncing assignments. All code in `index.js` and instructions in `SKILL.md` align with this stated purpose. It uses `playwright` for browser automation and `googleapis` for calendar integration, reading necessary configuration from environment variables and persisting Google OAuth tokens in `google-tokens.json`. There is no evidence of intentional data exfiltration, unauthorized execution, persistence mechanisms beyond the necessary browser context, or prompt injection attempts against the agent. The handling of sensitive browser sessions and OAuth tokens is inherent to the skill's functionality, not indicative of malicious intent.
Capability Assessment
Purpose & Capability
The skill's name and SKILL.md describe Edsby data fetch + Google Calendar sync and the index.js implements that using Playwright and googleapis — so the functionality matches the purpose. However, the registry metadata lists no required environment variables or config paths while both SKILL.md and index.js require multiple env vars (EDSBY_HOST, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI, GOOGLE_CALENDAR_ID, BROWSER_CONTEXT_PATH) and read/write local files (google-tokens.json and persistent browser context). This mismatch is incoherent and should have been declared.
Instruction Scope
SKILL.md and index.js instruct the agent to launch persistent browser contexts, perform interactive OAuth, scrape pages under the EDSBY_HOST domain, parse DOM selectors, and write/expect local token files. Those actions are within the claimed scope (fetching grades/assignments and syncing calendar), but they also imply broad access to local filesystem and any browser profile provided via BROWSER_CONTEXT_PATH. Instructions around 'scheduled checks' and 'persistent sessions' mean this skill may repeatedly access user data autonomously if invoked — the runtime instructions are not narrowly scoped and rely on local files not declared to the registry.
Install Mechanism
There is no explicit install spec in the registry, but package.json lists substantial dependencies (playwright and googleapis). Playwright will typically download browser binaries during install which increases footprint and network activity. The absence of an install spec combined with heavy dependencies is a moderate concern (it is traceable/public packages, not an arbitrary URL), but users should be aware of the extra browser downloads and system requirements.
Credentials
The code requires multiple sensitive environment settings and credentials (Google OAuth client ID/secret, redirect URI, calendar ID, and an Edsby host), but the registry metadata declares none. The skill also expects and reads a local file 'google-tokens.json' (persisted OAuth tokens) and uses a persistent browser context path (defaulting to HOME). Requesting and storing OAuth tokens and persistent browser sessions is proportionate to the stated functionality, but not declaring these requirements is a red flag; additionally, using a browser context path could allow access to unrelated browser data if misconfigured.
Persistence & Privilege
always:false (normal) and the skill does not request system-wide configuration changes. However, it persists browser contexts and token files to disk and provides a 'daily check' tool that could be scheduled or invoked automatically by the agent. Combined with the credential handling above, persistent on-disk tokens and browser profiles increase blast radius if the skill is granted those credentials and allowed autonomous invocation.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install edsbygrades
  3. After installation, invoke the skill by name or use /edsbygrades
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Renamed documentation file from SKILLS.md to SKILL.md for consistency. - No change to skill functionality or configuration.
v1.0.0
Initial release: Integrates Edsby student data with reporting and Google Calendar sync. - Fetches classes, grades, and assignments from Edsby using browser relay. - Generates personalized reports and bi-weekly grade summaries with improvement tips. - Syncs assignment due dates directly to Google Calendar. - Schedules daily assignment checks and synchronizations. - Requires configuration of Edsby host, Google API credentials, and secure browser sessions.
Metadata
Slug edsbygrades
Version 1.0.1
License
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Edsby Grades Board?

Fetches Edsby student data to generate grade reports, provide bi-weekly summaries with tips, and sync assignments to Google Calendar. It is an AI Agent Skill for Claude Code / OpenClaw, with 984 downloads so far.

How do I install Edsby Grades Board?

Run "/install edsbygrades" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Edsby Grades Board free?

Yes, Edsby Grades Board is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Edsby Grades Board support?

Edsby Grades Board is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Edsby Grades Board?

It is built and maintained by Lystea11 (@lystea11); the current version is v1.0.1.

💬 Comments