Build a Student Event Radar with Claude

Schedule a source-backed Claude briefing for student events and hackathons.

Introduction

30 Second Summary

Finding worthwhile student events often means checking several websites. Important details can be scattered across listings or already out of date.

In this project, you will build a scheduled Student Opportunity Radar in Claude Max. Each weekly briefing will gather source-linked opportunities from Luma, Eventbrite, Meetup, Devpost, Major League Hacking, and broader web research.

What You'll Build

When your radar runs, you will see a source-linked weekly briefing with separate event and hackathon recommendations.

By the end of this project, you'll have:

A personalized weekly briefing that surfaces AI, technology, and useful business opportunities based on your location preferences. Cross-posted listings appear once with a direct source link.
Distinct General Events and Hackathons sections. Each section gives you the details needed to judge that opportunity type.
An action-ready recommendation that highlights urgent deadlines plus the strongest opportunity for the week. A networking plan gives you conversation starters plus a follow-up action.
Secret Mission: A reprofiled radar for a non-technical student that changes its recommendations without changing the core research workflow.

Are There Any Prerequisites?

You need your existing Claude Max account. You can create or sign in to a Luma account during the project.

The project adds no extra cost because Luma Plus is not required.

Before We Start

A useful Student Opportunity Radar needs a clear audience and purpose before you configure it. This is your moment to define which student it serves and what each weekly briefing should help them decide or do.

Connect Claude to Luma

Your radar now has a defined audience. It still needs a dependable event-platform source before broader research can produce grounded recommendations.

In this step, you'll connect Claude to Luma. A live event search proves that the connection can support your weekly radar.

In this step, get ready to:

Confirm that Claude offers a task scheduling route.
Authorize Luma as a Claude connector.
Run a live event search through Luma.

Confirm Claude's scheduling access

Claude can schedule recurring work through the unified task experience or the Scheduled area. Your interface may show either route during the rollout.

Click your preferred web browser in the Mac Dock.
Enter claude.ai in the browser address bar.

You'll see your Claude workspace or a sign-in screen.

Sign in to your Claude Max account if prompted.
Check whether your Claude workspace offers the unified task experience or shows Scheduled in the left sidebar.

Good, you now know where the weekly automation will live.

Can't Find a Scheduling Route?

Confirm that you signed in with the account that has Claude Max.
Refresh the Claude page to load the latest interface available to your account.

Ask for help if the scheduling route is still missing: help me confirm whether my Claude Max account can access scheduled tasks.

Connect and authorize Luma

A connector gives Claude permission to query Luma directly. Authorization links the two accounts.

A regular Luma account is enough. Luma Plus is not required.

Enter claude.ai/directory/luma in the browser address bar.
Click Connect.

You'll see the Luma sign-in or authorization flow.

✔️ I have a Luma account

Use your existing Luma account for this connection.

ⓧ I need a Luma account

Create a regular Luma account before continuing with authorization.

Create your Luma account by following the on-screen setup prompts.

Click Authorize on the Luma authorization screen.

That connection is ready. Luma is now authorized for your Claude account.

Why Start With Luma?

Luma gives Claude a direct source for public events filtered by keyword, location, or date range. This platform-first approach gives the radar a grounded starting point before broader research fills any gaps.

Authorization Not Completing?

Return to claude.ai/directory/luma to restart the connection flow.
Confirm that your browser allows the Luma sign-in page to load.
Complete any unfinished Luma account prompts before selecting Authorize again.

Get targeted help here: help me complete the Claude-to-Luma authorization.

Enable Luma and run a live search

Authorization makes Luma available to Claude. You still enable the connector in the conversation that performs the search.

Start a new conversation from the Claude sidebar.
Click the + button beside the message box.

You'll see the tools available for this conversation.

Choose Connectors.
Turn on the Luma toggle.

Luma is now active in this conversation.

Choose the search location: your city or nearest major city.

Before you send the search, do you expect Luma to find several matches or report none?

Send the verification search by pasting this request into Claude:

Use Luma to search for public AI, technology, or business events in [[WORKING_LOCATION="your city or nearest major city"]] during the next 30 days. Return the matching events. If none match, clearly report that no events matched.

What Does This Verification Prove?

The three interest areas test whether Luma can search using relevant event keywords.
The location and 30-day window test the connector's geographic and date filtering.
A matching event list or an explicit no-match result proves that the live search completed.

Claude should complete the Luma search. You'll see matching public events or a clear statement that no events matched.

Luma Did Not Run?

Click the + button in the current conversation.
Choose Connectors.
Turn on Luma if its toggle is disabled.
Send the verification request again.

Get help with the failed search here: help me make Claude use the Luma connector.

Your direct event source is working. Next up, you'll use it to create the radar's first opportunity briefing.

Create a Baseline Briefing

Your live Luma search proved that Claude can reach a dependable event source. A broader briefing now tests whether the research loop can gather useful opportunities from several platforms.

The first baseline gives you visible proof that this wider search works. Using one shared format creates a result you can inspect before refining the workflow.

In this step, get ready to:

Choose the boundaries for this one-time search.
Generate one chronological list from named event sources.
Compare how the shared fields handle each opportunity type.

Choose your search preferences

Search preferences define which opportunities count as practical for you. Clear boundaries keep the briefing focused on events you could realistically attend.

Define your local search area as your city or nearest major city within your acceptable travel radius.
Set your online-event preference to include online events or in-person only.

Your location boundaries are now recorded. Your online preference is also ready for the briefing.

Set the search window to the next 30 days.

Generate one combined opportunity list

A source-first discovery process begins with named platforms. This gives each opportunity a clear path back to its listing.

How does the baseline search?

Luma uses the existing connector to search public events.
Event pages from Eventbrite are found through web research.
Meetup contributes event listings that match the chosen location.
Devpost contributes upcoming online or in-person hackathons.
Major League Hacking contributes opportunities from its official season schedule.

Prepare the baseline request by copying the text below:

Create a one-time Student Opportunity Radar briefing.
Use [[WORKING_LOCATION="your city or nearest major city"]] as the working location.
Use [[TRAVEL_RADIUS="your acceptable travel radius"]] as the acceptable travel radius.
Use [[ONLINE_EVENT_PREFERENCE="include online events or in-person only"]] as the online-event preference.
Use the next 30 days as the search window.

Search Luma through the connector.
Use web research for Eventbrite.
Use web research for Meetup.
Use web research for Devpost.
Use web research for Major League Hacking.

Find up to eight upcoming opportunities.
Include AI opportunities.
Include technology opportunities.
Include business opportunities.
Include hackathons.
Present every result in one chronological list.

For each opportunity, include:
- title
- date
- format
- location
- published cost when available
- source link

What does this request do?

The first section inserts your search preferences.
The second section assigns a named source for each part of the research.
The third section sets one shared list with a limit of eight opportunities.
The final section defines the details every result must include.

Paste the request into the message box in the Claude conversation from earlier.

Before you submit the request, consider whether every opportunity type will be equally easy to compare with the same fields.

Submit the request by pressing Enter.

What should I see?

One combined list ordered chronologically.
No more than eight upcoming opportunities.
Coverage that can include AI opportunities.
Coverage that can include technology opportunities.
Coverage that can include business opportunities.
Coverage that can include hackathons.
Each item includes a title.
Each item includes a date.
Each item includes a format.
Each item includes a location.
Each item includes any published cost.
Each item includes a source link.

Missing sources or fields?

Return to the Claude conversation from earlier if Luma is missing from the search.
Compare the pasted request with the full prompt above if the response has no source links.
Widen your travel radius if the list has too few local matches.

help me fix a baseline briefing with missing sources or fields.

Your first cross-source briefing is live. You now have concrete opportunities to compare.

Inspect the shared format

The combined list makes each opportunity look comparable because every entry uses the same fields. The comparison now reveals where that shared format runs out of detail.

Select one talk or general event from the combined list.
Judge its relevance using the event topic.
Judge its usefulness using the networking value.
Select one hackathon from the combined list.
Compare that hackathon with the decision details below.

What does the comparison reveal?

Talks or general events can be judged from topic fit. Networking value shows whether attending could support the student's goals.

Eligibility determines whether the student can enter the hackathon.
Team requirements show whether the student needs collaborators.
Submission requirements show what the student must produce.
A deadline shows when the student must act.
Build commitment shows how much work the opportunity demands.

The baseline fields are enough to screen many talks or general events. Hackathons need a dedicated evaluation format.

That first research loop is working. Next, you'll turn this combined baseline into a reusable briefing with separate opportunity formats.

Define Profiles and Event Schemas

Your baseline briefing proves that the Student Opportunity Radar can find source-linked opportunities through Claude.

The combined list also mixes categories that need different evidence. Talks and general events can be judged by topic and networking value. Hackathons also require eligibility, team, submission, deadline, and build-commitment details.

The baseline also ties its recommendations closely to one learner's interests. In this step, you will move those preferences into a reusable Interest Profile. You will organize research through source-first discovery. You will also define category-specific schemas for the two opportunity types.

In this step, get ready to:

Make the learner's interests swappable through an Interest Profile.
Set a source-first discovery order for the radar.
Define category-specific output schemas.

Turn preferences into a reusable profile

Personal preferences belong in one labeled block that can be replaced without rewriting the research workflow. This keeps your current focus on AI while making the radar adaptable for another student.

Switch back to the Claude conversation that contains your baseline briefing.
Create the reusable profile by sending this prompt to Claude:

Revise my baseline Student Opportunity Radar instructions. Keep my existing working location, acceptable travel radius, online-event preference, and 30-day search window unchanged.

Add this Interest Profile:
- Primary interests: AI and technology.
- Secondary interests: business, entrepreneurship, product, and career talks.
- Exclusions: sales-focused events and unrelated industries.

Return the updated instructions as one reusable block. Do not run the search in this response.

What Does This Prompt Change?

The profile isolates personal interests from the reusable research workflow.
The primary interests keep AI and technology at the center of the briefing.
The secondary interests retain useful business opportunities.
The exclusions filter sales-focused events and unrelated industries.

Review the reusable instruction block returned by Claude.

You should see a labeled Interest Profile containing the specified primary interests, secondary interests, and exclusions. Your existing search preferences should remain unchanged.

Good progress. Your preferences now sit in one block that can be replaced without rebuilding the radar.

Did Claude Change Your Search Preferences?

Check the returned instructions against the working location from your baseline request.
Check the returned instructions against your existing travel radius.
Ask Claude to restore any preference that changed.

Ask for help to restore my baseline search preferences.

Set a source-first discovery order

A platform-first search starts with sources designed to publish opportunities in a consistent format. Broader web research then fills gaps from relevant organizer pages.

Why Platform-First Discovery?

A web-only search can offer broad coverage. Its metadata can be inconsistent across pages. Source attribution and duplicate detection also become harder.

Event platforms provide a stronger starting point. Broader web research remains useful as a focused fallback for opportunities that the primary sources miss.

Add the discovery order to the reusable instructions by sending this prompt:

Update the reusable Student Opportunity Radar instructions with this source-first search order.

General Events:
- Search Luma, Eventbrite, and Meetup first.

Hackathons:
- Search Devpost, Major League Hacking, and relevant Luma listings first.

Gap filling:
- Use broader web research only to fill gaps.
- Limit gap-filling sources to university, accelerator, coworking-space, community, and organizer pages.

Return the complete updated instructions. Keep the Interest Profile and existing search preferences unchanged.

How Does the Search Order Work?

General Events begin with Luma, Eventbrite, and Meetup.
Hackathons begin with Devpost, Major League Hacking, and relevant Luma listings.
University and organizer pages fill gaps after the primary sources have been searched.
The separate source groups preserve useful coverage for each opportunity category.

Review the complete source order returned by Claude.

You should see separate source groups for General Events and Hackathons. Broader web research should appear only as the gap-filling stage.

Your radar now has a clear research hierarchy. Each category starts with the sources most suited to it.

Is Web Research Still Listed First?

Check that the General Events source group begins with the three event platforms.
Check that the Hackathons source group begins with the dedicated hackathon sources.
Ask Claude to move broader web research into the gap-filling stage.

Ask for help to fix my source-first discovery order.

Give each category its own schema

A schema defines the fields that every result in a section should include. Separate schemas let you evaluate a talk by relevance and networking value while checking a hackathon's eligibility and build commitment.

Add the category-specific schemas by sending this prompt:

Update the complete reusable instructions with two output schemas.

General Events fields:
- Relevance.
- Audience.
- Date.
- Format.
- Location.
- Published cost.
- Registration link.
- Networking value.

Hackathons fields:
- Theme.
- Format.
- Eligibility.
- Team requirements.
- Application or submission deadline.
- Duration.
- Published prizes.
- Beginner fit.
- Official rules or registration link.

Return the complete updated instructions. Keep the Interest Profile, source order, and existing search preferences unchanged. Do not run the briefing in this response.

Why Use Two Schemas?

The General Events schema focuses on relevance, practical attendance details, and networking value. These fields help you decide whether a talk or meetup deserves your time.

The Hackathons schema captures participation requirements and build commitment. Its deadline, duration, prize, and beginner-fit fields support a different decision.

Review the complete reusable instructions returned by Claude.

You should see distinct General Events and Hackathons schemas. The Interest Profile and source-first discovery order should still appear above them.

Your complete instruction block should now match the reference below.

✔️ Awesome, I've got everything!

Your reusable instructions now contain the Interest Profile, source-first discovery order, and category-specific schemas.

ⓧ I'd like to double check the full instructions

Compare your complete instruction block with this reference:

Student Opportunity Radar

Research upcoming opportunities using my existing working location, acceptable travel radius, online-event preference, and 30-day search window.

Interest Profile
- Primary interests: AI and technology.
- Secondary interests: business, entrepreneurship, product, and career talks.
- Exclusions: sales-focused events and unrelated industries.

Source-first discovery
- General Events: Use Luma, Eventbrite, and Meetup.
- Hackathons: Use Devpost, Major League Hacking, and relevant Luma listings.
- Use broader web research only to fill gaps through university, accelerator, coworking-space, community, and organizer pages.

Output
Create distinct General Events and Hackathons sections. Keep business events when they support the Interest Profile.

For each General Event, show relevance, audience, date, format, location, published cost, registration link, and networking value.

For each Hackathon, show theme, format, eligibility, team requirements, application or submission deadline, duration, published prizes, beginner fit, and official rules or registration link.

How Is This Instruction Block Organized?

The first section stores the swappable learner preferences. The second section establishes the platform-first research order.

The final section separates the two opportunity categories. Each category receives the fields needed for a useful decision.

Before you run the revised briefing, which part of the old combined list do you expect to change most?

Generate the revised briefing by sending this prompt to Claude:

Run the finalized Student Opportunity Radar instructions now. Keep relevant business events. Return separate General Events and Hackathons sections.

What Does This Run Test?

This run applies the reusable profile and source order to your existing search preferences. It also tests whether each opportunity category receives its dedicated fields.

You should see distinct General Events and Hackathons headings. Each section should use its own fields with source links.

Relevant business events should remain under General Events. Hackathons should show their dedicated eligibility, team, deadline, duration, prize, beginner-fit, and rules fields.

That separation is the core design upgrade. Your radar now evaluates each opportunity using evidence that fits the commitment.

Are the Categories Still Combined?

Check that the finalized instructions explicitly request the General Events heading.
Check that the finalized instructions explicitly request the Hackathons heading.
Check that the two schemas appear as separate sections in the instructions.

Ask for help to separate my opportunity briefing.

Your radar now has reusable preferences and category-specific evaluation rules. Next, you will strengthen its source checks, ranking logic, and networking guidance.

Add Quality Rules and Networking Prep

Your radar already separates General Events from Hackathons. Each opportunity now has the right evaluation fields.

Stale dates make a long list unreliable. Duplicate listings make it noisy.

In this step, you'll add source verification. You'll also add deduplication.

Separate ranking rules will surface the strongest options. Networking guidance will turn the top recommendation into a practical plan.

In this step, get ready to:

Add quality rules for trustworthy listings.
Rank General Events separately from Hackathons.
Finish the briefing with a recommendation plus networking guidance.

Add source checks and duplicate handling

Quality rules set the minimum evidence required for every recommendation. They prevent an incomplete listing from sounding more certain than its source.

Return to the Claude conversation containing your Finalized Briefing Instructions.
Add the quality rules by submitting this instruction:

Include only future opportunities with working official event or registration pages; provide direct source links and originating platforms; never infer missing details; label missing details `Not published`; and merge cross-posted listings.

How do these rules improve the briefing?

Working official pages keep expired opportunities out of the report.
Direct source links make every recommendation traceable.
The Not published label preserves uncertainty when a source omits a date, price, prize, eligibility rule, or deadline.
Merging cross-posted listings stops one opportunity from occupying several ranking positions.

Review Claude's updated briefing instructions.

You should see the new source checks inside the reusable instructions. The earlier General Events and Hackathons schemas should remain in place.

Did Claude replace an existing schema?

Tell Claude to preserve the existing General Events fields while adding only the new quality rules.
Tell Claude to preserve the existing Hackathons fields while adding only the new quality rules.

Ask for targeted help if the reusable instructions lost an earlier section: help me preserve my existing briefing schemas while adding quality rules.

Rank each opportunity category separately

General Events reward relevance to your goals. Their networking value also matters.

Hackathons require eligibility checks. Their build commitment also affects whether they fit your week.

Add category-specific ranking by submitting this instruction:

Rank General Events by interest fit, location or online fit, timing, published cost, networking value, and registration urgency. Rank Hackathons by theme fit, eligibility, time commitment, beginner fit, deadline urgency, and published prize or learning value.

Why use separate rankings?

General Events rise when they fit your interests.
Practical access influences the order of General Events.
Networking value helps useful conversations outrank weak matches.
Hackathon eligibility acts as a participation gate.
Time commitment measures whether a hackathon fits your availability.
Beginner fit shows whether the opportunity matches your current experience.
Deadline urgency moves time-sensitive hackathons higher.

Review the updated ranking rules inside the reusable instructions.

You should see one ranking model for General Events. You should see a different ranking model for Hackathons.

Do both sections use the same ranking?

Ask Claude to keep the General Events ranking criteria attached only to General Events.
Ask Claude to keep the Hackathons ranking criteria attached only to Hackathons.

Use targeted help if the criteria remain mixed: help me separate the two ranking models.

Add action sections and run the briefing

A ranked list still leaves the next move to you. Three action sections convert the research into a deadline view, one recommendation, and an event-specific networking plan.

Add the action sections by submitting this instruction:

Include Registration Deadlines, Best Opportunity This Week, and Networking Prep with a goal, two event-specific conversation starters, a person or role to seek out, and a follow-up action.

What do the action sections add?

Registration Deadlines collects opportunities that need prompt action.
Best Opportunity This Week forces the briefing to make one recommendation.
Networking Prep turns that recommendation into a practical event plan.
Event-specific conversation starters avoid generic small talk.

Review the cumulative Finalized Briefing Instructions.

Use the tabs below to confirm that every earlier source rule and schema remains in the strengthened version.

✔️ Awesome, I've got everything!

Great. Your cumulative instructions now include quality checks, separate rankings, and action guidance.

ⓧ I'd like to double check the full code

Compare your complete Finalized Briefing Instructions with this reference:

Reusable source-first Student Opportunity Radar instructions. General Events sources are Luma, Eventbrite, and Meetup; Hackathon sources are Devpost, Major League Hacking, and relevant Luma listings; university, accelerator, coworking-space, community, and organizer pages fill gaps only. General Events fields are relevance, audience, date, format, location, published cost, registration link, and networking value. Hackathons fields are theme, format, eligibility, team requirements, application or submission deadline, duration, published prizes, beginner fit, and official rules or registration link. Include only future opportunities with working official event or registration pages; provide direct source links and originating platforms; never infer missing details; label missing details `Not published`; and merge cross-posted listings. Rank General Events by interest fit, location or online fit, timing, published cost, networking value, and registration urgency. Rank Hackathons by theme fit, eligibility, time commitment, beginner fit, deadline urgency, and published prize or learning value. Include Registration Deadlines, Best Opportunity This Week, and Networking Prep with a goal, two event-specific conversation starters, a person or role to seek out, and a follow-up action.

Before you run it, predict whether the report will finish with a clear next action.

Run the strengthened briefing by submitting this prompt:

Re-run the briefing and inspect the changes.

What should the strengthened briefing show?

Only future opportunities should remain.
Every listing should include a direct source link.
Every listing should name its originating platform.
Cross-posted duplicates should appear once.
General Events should follow their own ranking criteria.
Hackathons should follow their own ranking criteria.
The report should finish with all three action sections.

Inspect the date for every listed opportunity.
Check the direct source link for every listed opportunity.
Check the originating platform for every listed opportunity.

You should see only future dates. Each item should show a direct source link. Its originating platform should also appear.

Scan the opportunity titles for duplicate cross-postings.

Repeated listings for the same opportunity should be merged into one entry.

Scroll to the end of the strengthened briefing.

You should see Registration Deadlines followed by Best Opportunity This Week. Networking Prep should complete the report.

Networking Prep should give you one goal. It should include two event-specific conversation starters.

It should identify one person or role to seek out. It should finish with one follow-up action.

That is the research loop working. Your radar now points to one verified opportunity with a concrete networking plan.

Does the briefing still look incomplete?

Ask Claude to remove any opportunity without a future date.
Ask Claude to merge any repeated cross-posting that remains.
Ask Claude to anchor Networking Prep to the recommended opportunity.

Use the report itself when asking for help: help me find which quality rule my strengthened briefing missed.

Your radar now filters weak listings and surfaces a practical next move. Next, you'll schedule it to refresh every week.

Schedule the Weekly Radar

Your strengthened briefing already produces a ranked result backed by direct sources. However, it only helps when you remember to run it.

A scheduled task in Claude refreshes the radar every Monday at 8:00 AM local time. It uses web research plus the authorized Luma source.

In this step, get ready to:

Schedule the finalized briefing as a weekly task.
Run the scheduled task on demand.
Confirm the report against its official source pages.

Schedule the recurring task

Scheduling stores the finalized briefing instructions inside Claude. Its weekly cadence triggers a fresh opportunity search without another manual prompt.

Claude accounts may show the unified Claude experience or the Cowork interface. Both routes create the same recurring task.

Select the tab that matches your Claude interface.

Unified Claude Experience

Switch back to the Claude conversation containing your finalized briefing instructions.
Ask Claude to create a scheduled task named Student Opportunity Radar from those instructions.
Set the cadence to every Monday at 8:00 AM local time.
Require the task to use Claude web research plus the authorized Luma connector.
Review the proposed task to confirm the finalized briefing instructions remain unchanged.
Click Schedule.

Cowork Interface

Click Scheduled in the left sidebar.
Click New task.
Choose Create with Claude.

The task editor is now ready for the instructions you developed earlier.

Provide the finalized briefing instructions from your earlier conversation.
Name the task Student Opportunity Radar.
Set the cadence to every Monday at 8:00 AM local time.
Require the task to use Claude web research plus the authorized Luma connector.
Review the proposed task to confirm the finalized briefing instructions remain unchanged.
Click Schedule.

You should see Student Opportunity Radar in Scheduled with a Monday cadence at 8:00 AM local time.

That weekly routine is handled. Claude now owns the refresh that was easy to forget.

Can't find the scheduled task?

Confirm Claude is using the same Max account that contains your briefing.
Check the alternative scheduling route above if your interface does not match the first tab.

Ask for help if the scheduling controls still do not appear. Help me find the scheduled-task controls in my Claude Max interface.

Run the radar on demand

An on-demand run tests the exact task you just scheduled. It proves the automation can produce the full report before Monday arrives.

Return to Scheduled.
Select the Student Opportunity Radar task.

Before you start the run, which sections do you expect the scheduled report to contain?

Click Run on demand.

Once the run finishes, you'll see a completed opportunity briefing inside the task.

Confirm the report contains General Events.
Confirm the report contains Hackathons.
Confirm the report contains Registration Deadlines.
Confirm the report contains Best Opportunity This Week.
Confirm the report contains Networking Prep.
Confirm the recommendations include direct source links.

The scheduled report now contains every required action section. Its recommendations also include links back to their sources.

Is a report section missing?

Compare the saved task instructions with the finalized briefing instructions from earlier.
Restore any missing section requirement in the saved instructions.
Click Run on demand again.

Use this prompt if the saved task still produces an incomplete report. Help me compare my scheduled Student Opportunity Radar instructions with the finalized requirements and identify why a report section is missing.

Validate the source links

A direct source link gives each recommendation an audit trail. Comparing both opportunity categories checks the briefing against the pages learners would actually use.

Before you open the links, do you expect every displayed detail to agree with its source page?

Open one direct source link from General Events.
Compare the source page's date with the briefing.
Compare the source page's format with the briefing.
Confirm the page offers the registration destination described in the briefing.

All three General Events details should agree with the briefing.

Return to the completed report in Scheduled.
Open one direct source link from Hackathons.
Compare the source page's date with the briefing.
Compare the source page's format with the briefing.
Confirm the page leads to the registration or official rules destination described in the briefing.

The Hackathons source should also agree with the report. Together, both checks prove the radar leads to current opportunity details.

Does a source page show different details?

The current official page is the source of truth. Event details can change after a briefing has been generated.

Return to the scheduled task.
Click Run on demand to refresh the report.
Repeat the source-link comparison.

Ask for help if the refreshed report still disagrees with the source. Help me identify why my scheduled briefing disagrees with an official event page.

Your Student Opportunity Radar now refreshes every Monday without depending on your memory. You have also proved its scheduled report against live source pages.

Secret mission

Reprofile the Radar for a Different Student

Test the radar with a non-technical student profile. The recommendations should shift to the new field while the source checks, rankings, deadlines, and networking guidance stay intact.

Clean Up Your Resources

This project adds no subscription or cloud-resource cost beyond your existing Claude Max plan. Decide whether to keep the radar active, pause its weekly schedule, or remove its resources.

Resources you used:

An authorized Luma connector available to Claude.
A Student Opportunity Radar task scheduled for every Monday at 8:00 AM local time.

Keep everything running

No action needed. Choose this if you want Claude to continue producing a fresh opportunity briefing every Monday.

Leave the Luma connector enabled so the radar can search that event source.
Leave the Monday task active so the weekly schedule continues.
Keep your finalized briefing instructions available for future profile changes.

Pause - I'll come back to this later

Pause the scheduled task to stop weekly reports while keeping its instructions available. The Luma connection stays authorized for future searches.

Switch back to Claude.
Click Scheduled in the left sidebar.
Select the Monday 8:00 AM Student Opportunity Radar task.
Click Pause in the task controls.

You'll see the task change to a paused state. It stops producing Monday briefings until you resume it.

Delete - I don't want to use this again

Deleting these resources can feel final. You can rebuild both from the instructions you already saved in Claude.

Switch back to Claude.
Click Scheduled in the left sidebar.
Select the Monday 8:00 AM Student Opportunity Radar task.
Use the task's Delete control to remove the recurring schedule.
Return to Claude's connector settings.
Find Luma in the configured connectors.
Use the connector's removal option to disconnect Luma from Claude.

You should no longer see the weekly task under Scheduled.

Luma should no longer be available as a connected source in Claude.

Nice Work!

You did it! You built a weekly Student Opportunity Radar in Claude.

You've learned how to:

Build a source-first briefing that searches Luma plus official event sources for relevant future opportunities.
Evaluate General Events and Hackathons through separate category-specific schemas backed by source checks, deduplication, missing-data rules, and rankings.
Schedule a Monday briefing in Claude that highlights registration deadlines, recommends the week's best opportunity, and supplies networking preparation.
Secret Mission: Reprofile the same radar for a non-technical student while preserving its verification, ranking, action, and networking rules.

Ready to quiz yourself?