90-Minute Meeting Minutes in 11 Seconds: A Claude Code Skill for Non-Engineers to Build in 30 Minutes [Business Scenario 1]

I imagine many of you spend an hour every week formatting minutes for 90-minute meetings.

That hour is not actually your job.
It just keeps coming back to you every week because no one else does it.
At 1 hour × 52 weeks, that is 52 hours a year—roughly 6 business days of your life—spent on transcription work that anyone could do. This grows even more during busy meeting seasons.

And the scary part is that this time does not contribute to your career evaluation.
I have never heard of anyone getting a promotion because they were good at formatting meeting minutes.

However, there is hope.
In a real-world example from the Hakky Handbook, minutes for a 90-minute meeting were generated in 11 seconds. That is an efficiency gain of about 490 times. By using the Skills feature of Claude Code (an AI assistant that runs on your own PC), that hour on Monday morning is replaced by 10 seconds of calling your AI subordinate.

In this article, I will provide the steps to build your own meeting minutes Skill in 30 minutes. At the end, I have also included examples of how to convert this experience into a single line for your resume.

What you will learn in this article

• 4 steps to build a meeting minutes Skill in 30 minutes

• How your Monday mornings will change after completing the meeting minutes Skill

• Skill implementation concept (no coding required; just give instructions via chat)

• 3 patterns for converting your custom Skill into a single line for your resume

• Applications for peripheral meeting tasks (action item extraction, weekly reports)

I want to quit being a meeting minutes professional

If you break down the time spent formatting meeting minutes, it looks like this: transcribing the recording, extracting key points, organizing who said what, confirming decisions, turning tasks into action items with deadlines, formatting for Slack sharing, and tagging relevant stakeholders. All of this takes about an hour.

You have surely wondered many times why this is your job. The core work of a sales professional is creating proposals and going to business meetings. Formatting minutes is the same regardless of who does it, but because no one else does it, it keeps coming back to you every week. It is a structure where 52 hours a year—6 business days of your life—vanish into transcription work that anyone can do.

Many of you have likely tried to improve efficiency with ChatGPT. However, you probably haven't saved as much time as you expected due to file attachment limits, the inability to maintain context across multiple meetings, and the hassle of re-entering the same instructions every time. Many people have had that experience.

The tool to overcome that barrier is Claude Code.

How Claude Code changes meeting minutes

Claude Code is an AI assistant provided by Anthropic (an AI development company) that runs on your PC.
Cowork (a GUI version that can be operated via a standard chat screen) was released in January 2026 and became the official version in April. Now, even non-engineers who are intimidated by black screens can use it with the same feel as ChatGPT.

There are two major differences from ChatGPT.

The first is that it can directly read and write files on your PC.
While ChatGPT can only read what you attach, Claude Code can read all dozens of meeting minutes in a folder if you specify the entire folder.

The second is a mechanism called Skills (dedicated AI subordinates trained in work procedures).
This is a feature released by Anthropic on October 16, 2025, that allows you to call up routine tasks with the feeling of pressing a single button.
Once you teach it the procedure just once, from the next time on, it will work just by you saying, 'Organize last week's meeting minutes.'

And a practical example is the Hakky Handbook article mentioned at the beginning.
Meeting minutes for a 90-minute meeting were generated in 11 seconds, an efficiency improvement of about 490 times.
This is the result of having Claude learn the format of the minutes, eliminating the need to re-instruct the same thing every week.

Those who felt that ChatGPT was 'convenient but tedious to instruct every time' will be able to experience this difference.
Now, let's actually create a Skill in 30 minutes.

4 steps to create a meeting minutes Skill (completed in 30 minutes)

From here on, the procedure really does not involve writing code.
As a preliminary preparation, please subscribe to Claude Pro (3,100 yen/month, calculated at $1 = 155 yen) and install the Claude desktop app (Cowork).
You will be able to use Claude Code for the same monthly fee as ChatGPT Plus.

Step 1 (5 minutes): Preparing the meeting minutes folder

First, create one folder on your PC dedicated to meeting minutes.
The location does not matter. It can be on your desktop or in your documents.

Example of folder name: 'MeetingMinutes2026'

Collect the meeting minutes from the past 2-3 months in it.
If the minutes are already saved separately as Word or text files, copying them is fine.

Decide on just one rule for file names.
The recommendation is the format 'YYYYMMDD_MeetingName.txt'.
Example: '20260508_RegularMeeting.txt', '20260501_SalesMTG.txt'

With this rule, Claude Code can correctly identify 'last week's meeting minutes'.

Step 2 (10 minutes): Specify the meeting minutes folder in Cowork

Launch the Claude desktop app.
There is a folder icon at the bottom left of the screen, so click this and select the 'MeetingMinutes2026' folder you created earlier.

Now, Claude Code is in a state where it can read the entire contents of that folder.
Unlike ChatGPT attachments, you do not need to upload files every time.

As the first instruction, type this in.

Claude Code will then read the meeting minutes in the folder one by one and return the formatted results.
You can also summarize across multiple meeting minutes.

If the generated result is not what you expected, you can provide additional instructions.
Example: "Please also include the priority (High/Medium/Low) for decisions," or "Please mark action items without a deadline as 'To be confirmed'."

Through this interaction, you can refine the template for meeting minutes that suits your work.

Step 3 (10 minutes): Skill Creation (Save to CLAUDE.md)

Once the template is finalized, the next step is to turn it into a Skill.
This is where the true value of Claude Code shines.

Give Claude Code the following instruction:

Claude Code will then write out the organization procedure in Markdown format (text with simple formatting) and save it in the folder.
You do not need to edit the file directly.

This CLAUDE.md becomes the instruction manual for your AI assistant.
Since it is a text file, you can open and check it yourself later.

Step 4 (5 minutes): Operation Check

Finally, perform an operation check.
Add one new meeting minutes file to the folder.
Then, speak to Claude Code like this:

That's all.
If set up correctly, the same formatted result as in Step 2 will be returned in just about 10 seconds.
If there are parts that are not as expected, you can slightly modify CLAUDE.md or give Claude Code an additional instruction like "Please include XX from next time," and it will be reflected.

With this, your meeting minutes Skill is complete.
In 30 minutes, you have effectively added an AI assistant to your PC.

Monday morning after the meeting minutes Skill is complete

Imagine next Monday morning.

You arrive at the office at 9:00, brew some coffee, and open Cowork.
You type, "Organize last week's meeting minutes and output them for Slack sharing."
10 seconds later, formatted text with decisions and action items lined up appears on the screen.
You copy it, paste it into Slack, mention the relevant people, and send it.

By this point, you have finished in under 5 minutes.
One hour has shrunk to 5 minutes, and the remaining 55 minutes are returned to your main work (sales, HR, planning, etc.).

This concept can also be applied to the automatic creation of weekly reports.
In Uravation's 10 business automation examples, a reduction effect of 20 hours per month has been reported.
If you replace weekly and monthly routine tasks with Skills, it is calculated that you will get back 240 hours worth of time per year.

And another big factor is the psychological change. When the heavy work on Monday morning disappears, you feel depressed less often at the end of the weekend. This is more effective than just the time saved.

Application example: Turning peripheral meeting minutes tasks into Skills

Once the meeting minutes Skill starts running, you can turn peripheral tasks into Skills using the same 4 steps.

• Automatic extraction of action items: A Skill that extracts actions with assignees and deadlines from rough meeting notes. There is a case where it went from 45 minutes to 15 minutes (approx. 67% reduction) (Uravation 5 Non-Engineer Scenarios).

• Automatic distribution of monthly summaries: A mechanism that summarizes decisions and incomplete actions from the past month's minutes at the beginning of the month.

• Conversion to weekly reports: A Skill that extracts specific themes such as sales projects, HR, and planning across the board from meeting minutes and formats them into weekly reports.

If you start with the meeting minutes Skill and replace peripheral tasks one by one, the very structure of your work time will change.

Conversion to a resume

The meeting minutes Skill you created up to this point can actually be material that raises your market value by one level.
As of May 2026, there are over 47 Claude Code job openings posted on Forkwell Jobs, and the salary range for AI-related positions is moving at a higher level than average. We have entered an era where AI agent operation experience can be a line on your resume.

I have prepared three examples of how to convert this into a resume.

Example 1: Quantifying individual work reduction

The point is the initiative of having built it yourself and the concrete figure of 47 hours per year. What recruiters want to confirm is not whether you know AI, but whether you can use it to produce results. People who can quantify this will rarely be stopped at the document screening stage.

Example 2: Expanding to team deployment

When you expand the story from individual effectiveness to team deployment, the axis of evaluation shifts from individual efficiency to organizational contribution. If you can write this much, you will also be seen as a candidate for management.

Example 3: Continuous operation and improvement loop

This demonstrates an attitude of not just creating a number once and being done with it, but improving it while in operation. Anthropic's own marketing team also had a case where they compressed manual work from 4–8 hours to under 5 minutes through continuous improvement of an ad auditing Skill, and the power of continuous operation is especially valued in AI-native organizations (Rimo article).

The points recruiters are looking at are these three: quantified improvement, the proactivity of building it yourself, and continuous operation. As part of the company-wide adoption flow announced by Mercari at the Claude Code Meetup Japan #4 on April 10, 2026, the value of such achievements has clearly risen.

Summary + Bridge to the 84th installment

The minutes Skill is just the entry point. The true value of Claude Code is that it works for all tasks that have a fixed pattern. The scope of application, such as minutes, PDFs, data, emails, and Web automation, is not limited by job type.

In the next 84th installment, we will cover how to summarize a 500-page PDF in 5 minutes and the procedure to turn monthly Excel aggregation into a one-button experience. For those in HR, accounting, and planning where data and PDF processing are bottlenecks, it will have the same impact as the minutes Skill.

And as the culmination of the entire series, we will release the 'Claude Code 30 Skills Practice Pack' in the 88th installment (paid 500 yen).
We plan to include a total of 30 Skills that you can create by copy-pasting today: 10 for minutes, 10 for PDF/data, and 10 for email/Web.
A CLAUDE.md template collection and 3 types of blueprints for your own personal agent are also included.

Please use the Skill pack as a tool to transform the hour you spend on minutes every Monday morning into your future career.

• 82nd installment: 5 signs that people satisfied with ChatGPT should try Claude Code

• 83rd installment: Non-engineer minutes automation where 90-minute meeting minutes are completed in 11 seconds

• 84th installment: Summarizing a 500-page PDF in 5 minutes, the entry point for data/PDF processing

• 85th installment: 3 steps for email/Web automation to turn 600 minutes of daily email work into 30 minutes

• 86th installment: How to create your own AI subordinate that reads all your work files from the past 5 years

• 87th installment: A working portfolio that even non-engineers can create. How to attach it to your resume

• 88th installment (paid 500 yen): Claude Code 30 Skills Practice Pack

• 89th installment (paid 500 yen): Collection of real examples of salary increases through Claude Code experience

• 90th installment: Complete roadmap to getting a job offer in 30 days

If you found this article helpful, please press the heart mark; it will encourage me for the next article.

And what kind of routine tasks do you spend time on every week?
If you let me know in the comments, I will reflect it in the priority themes for the 88th installment's Skills pack.

Related articles

• The failures of 3 job changers who regretted paying 3,000 yen a month for ChatGPT Plus, and why the free version was enough

• Spring 2026: The salary premium earned by job changers with AI skills. Comparing job openings and average annual salaries with data

• The truth behind the 3 seconds recruiters take to judge documents. Changes in the impression of job changers who utilize AI [with interview examples]