Automated summary
This skill automates adding a new project to the interactive portfolio gallery by running a script that updates Projects.tsx, registers the WebP cover image in ProjectSection.tsx, and converts source images.
Strengths
- Collapses a multi-file edit into a single command with well-documented parameters
- Automatically converts JPG/PNG covers to optimized WebP via cwebp
- Handles `<b>` HTML stack annotations and turns them into React JSX bold markup
- Includes an explicit verification checklist covering typecheck, lint, and image paths
Limitations
- Tightly coupled to this portfolio's exact file layout (Projects.tsx, ProjectSection.tsx, Icons.tsx)
- Assumes cwebp is installed locally
- Available icons are limited to the names predefined in Icons.tsx
Use it when you need to publish a new project entry into this portfolio's gallery without hand-editing the React components.
Don't use it in another repository or project, since the paths, components, and icon list are specific to this portfolio.
Security analysis
CautionThe skill performs legitimate local automation, but it invokes an unaudited helper script and modifies repository source files and assets. There is no evidence of network exfiltration, secret access, or destructive commands, so caution is appropriate rather than risky.
- •Executes a local Node helper script that modifies source files and writes image assets; the script contents are not included, so its exact behavior cannot be audited.
- •Requires local filesystem access and the external `cwebp` binary to convert/copy user-supplied image paths.
- •Contains hard-coded absolute `file:///Users/ali/...` paths, exposing developer-specific environment details and reducing portability.
Examples
Add a new project to my portfolio: name "Solar Tracker", icon "energy", duration "2024", description "Dashboard for <b>React</b> and <b>Node</b> solar monitoring.", cover "/Users/ali/Desktop/solar.jpg", links '[{"tooltip": "See source", "link": "https://github.com/ali/solar", "icon": "code"}]'Run the add-project script for a project called "Retro Snake" with icon "videoGame", duration "2022 - 2023", the description "Classic snake game rebuilt in <b>TypeScript</b>", and cover image at ./assets/snake.pngAfter adding the project, confirm it appears in Projects.tsx, the WebP is in the coverImages array, the file exists under public/images/projects, and run npm run typecheck and npm run lint.Add Project Skill
Use this skill when adding a new project entry to the interactive portfolio gallery dashboard.
Instructions
The helper script automates appending the project properties to Projects.tsx, adding the WebP cover image to ProjectSection.tsx coverImages, and converting the raw image assets.
Usage
Run the script from the repository root:
node .agents/skills/add-project/scripts/add-project.mjs \
--name "Project Name" \
--icon "icon_key" \
--duration "YYYY - YYYY" \
--description "Project description with optional <b>bold</b> stack annotations." \
--cover "/path/to/source_image.jpg" \
--links '[{"tooltip": "See source", "link": "https://...", "icon": "code"}]'
Parameter Details
--name: (Required) Display title of the project.--icon: (Required) Icon name mapping toIcons.tsx(e.g.security,energy,app,code,link,smartToy,videoGame,timer,chat).--duration: (Required) Date or duration string (e.g.,"2025","2023 - 2024").--description: (Required) Detailed description. HTML bold tags<b>...</b>are parsed into React JSX bold markup automatically.--cover: (Required) Absolute or relative path to the project's cover image. The script automatically converts JPG/PNG images to optimized.webpviacwebpand copies them topublic/images/projects/.--links: (Optional) JSON array string containing project link objects. Each link object supportstooltip,link, andiconproperties.
Verification Checklist
- Confirm that the new project is listed in Projects.tsx.
- Confirm that the WebP image is added to the
coverImagesarray in ProjectSection.tsx. - Verify that the optimized cover image exists at
public/images/projects/<project_slug>.webp. - Run
npm run typecheckandnpm run lintto ensure zero compilation or syntax errors.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/add-project-to-portfolio-ms2s7cva/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/add-project-to-portfolio-ms2s7cva' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/add-project-to-portfolio-ms2s7cva/download' --output '.skill-downloads/add-project-to-portfolio-ms2s7cva/SKILL.md.part' && mv '.skill-downloads/add-project-to-portfolio-ms2s7cva/SKILL.md.part' '.skill-downloads/add-project-to-portfolio-ms2s7cva/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/add-project-to-portfolio-ms2s7cva/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.