Manusで任意のスキルを実行
ワンクリックで
ワンクリックで
ワンクリックでManusで任意のスキルを実行
始める$pwd:
$ git log --oneline --stat
stars:9,892
forks:727
updated:2026年3月12日 14:11
ファイルエクスプローラー
SKILL.md
3 ファイル
readonly
$ install --global
$ download --local
$ useful --forSOC
Analyze and fix issues reported by Sentry in the Polar codebase.
Add a new Terraform Cloud variable for the Render-hosted backend across production, sandbox, and test. Declares the tfe_variable in terraform/global/{production,sandbox,test}.tf and the matching variable {} block in terraform/{production,sandbox,test}/variables.tf, then reminds the user to wire it into render.tf / the render_service module.
Local development environment management for Polar using Docker
Add a new translation locale to the Polar frontend. Walks through registering the locale, generating translations, wiring the generated file into the i18n package, and updating the public-facing docs. Expects the target locale's ISO 639-1 alpha-2 code (optionally with a BCP-47 region suffix, e.g. `pt-PT`).
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
A skill to add a new entry in the section "Backend Development" of the Polar Handbook. Those entries are there to explain concepts, tooling and best practices related to backend development, and are meant to be read by Polar developers.
| name | interview-task |
| description | Prepare an interview task for a candidate, as part of our hiring process. |
| user-invocable | true |
| allowed-tools | Bash(gh:*) Bash(git:*) |
This skill is a complete cookbook for creating an interview task for a candidate. It includes steps to create the necessary materials. The idea is to create a private repository for the candidate, and have an LLM agent draft a PR for a given task. The candidate will then be asked to review the PR, and provide feedback on it. This will allow us to evaluate the candidate's ability to understand the codebase, provide constructive feedback and good insights to get the task to the finish line.
If not provided in the invocation prompt, you should ask the user for the following information:
Run the script provided in this skill .claude/skills/interview-task/scripts/fork-repository with the candidate's name as an argument. This will create a private repository for the candidate.
The name of the candidate should be slugified (lowercase, ASCII, spaces replaced with hyphens) to be used in the repository name.
Example
.claude/skills/interview-task/scripts/fork-repository francois-voron
Run the script provided in this skill .claude/skills/interview-task/scripts/setup-remote with the candidate's slug and the branch name as arguments. This will add a remote pointing to the candidate's fork, fetch it, create the branch, and push it to the remote. The branch name should be descriptive of the task.
Example
.claude/skills/interview-task/scripts/setup-remote francois-voron add-new-feature
Use an LLM agent to draft a PR in the candidate's repository. The PR should be based on the prompt provided by the user. The LLM agent should create one or more commits that implement the changes described in the prompt.
Once the changes have been made, push the changes and create a pull request in the candidate's repository. The PR should be titled and described in a way that clearly communicates the changes that were made.
git push && gh pr create --title "Add new feature" --body "This PR adds a new feature that allows users to do X, Y, and Z."
Post a comment to this PR following the template below, asking the candidate to review the PR and provide feedback on it.
Hi <candidate>,
We have created this PR as part of our interview process. We would like you to review the changes and provide feedback on it. Please take your time to understand the codebase, and provide constructive feedback and good insights to get the task to the finish line.
## Expected Outcome
- A clear understanding of the changes made in the PR
- Constructive feedback on the implementation, including any potential issues or improvements that could be made
- A discussion on how to get the task to the finish line, including any additional changes that may be needed to complete the task
We **don't** expect you to actually implement the changes.
## Next Steps
Post your feedback as a comment on this PR, and we will review it together during our next interview session.
Command to post the comment:
gh pr comment <pr-number> --body '<body>'