Yu hailin
Community@changfengpro · No. 696, Fenghe South Avenue, Nanchang City, Jiangxi Province, China
My name is Yu hailin. I am a student from Nanchang Hangkong University. My major is embedded systems. I hope to contribute to the community.
Agent Skills by Yu hailin
Showing 79 vetted skills indexed across 1 GitHub repositories.
lark-mail
Compose, read, organize, and send Lark Mail messages via the lark-cli command line.
techdoc-writer
Converts engineering debugging sessions and git history into formal Rockchip-style technical documents.
lark-minutes
Search, download, upload, and edit Feishu Minutes recordings and AI artifacts via lark-cli.
shopify-editions-3d-site
Build scroll-driven 3D product launch microsites with Three.js scenes and editorial content sections.
api-design-principles
Design REST and GraphQL APIs using resource-oriented patterns, pagination, and versioning standards.
self-improving-agent
Captures skill experiences into multi-memory artifacts and proposes validated skill updates.
changfengpro
Enforces project coding and documentation conventions with mandatory lint checks.
write-coding-standards-from-file
Generates coding standards documents by analyzing syntax patterns in source files.
lark-openapi-explorer
Discovers native Feishu/Lark OpenAPI endpoints from official documentation and invokes them via lark-cli.
lark-skill-maker
Creates reusable Skill definitions that wrap Feishu OpenAPI operations via lark-cli.
lark-calendar
Manage Lark calendar events, attendees, freebusy queries, and meeting room bookings via lark-cli.
lark-workflow-standup-report
Generates daily schedule and pending task summaries from Lark calendar and task APIs.
session-technical-summary
Archive AI coding sessions into incremental Markdown and HTML technical summaries.
lark-wiki
Manage Feishu wiki spaces, members, and document nodes via lark-cli.
setup-matt-pocock-skills
Configure a repository's issue tracker, triage labels, and domain doc layout for engineering skills.
humanizer-zh
Detect and rewrite AI-generated writing patterns in Chinese text to sound natural.
reusable-solution-doc
Converts specific debugging experiences into generalized, reusable technical solution documents.
planning-with-files-zh
Organizes complex multi-step tasks using persistent Markdown planning files on disk.
lark-markdown
Create, fetch, patch, overwrite, and diff Markdown files in Feishu Drive.
handoff
Generates a handoff document summarizing the current conversation for a fresh agent session.
web-design-guidelines
Review UI code files against Vercel Web Interface Guidelines for accessibility and design compliance.
gitnexus-refactoring
Automates safe code renaming, extraction, and restructuring using GitNexus dependency graph analysis.
lark-note
Query Lark meeting note details and unified transcripts by note_id via lark-cli.
gitnexus-debugging
Trace bugs and errors through code execution flows using GitNexus graph queries.
Frequently Asked Questions About Yu hailin
FAQPage SchemaWhat tasks can I accomplish with changfengpro's skills?▼
You can operate the full Feishu/Lark suite (mail, docs, sheets, Base, calendar, OKR, approvals, IM, video meetings, drive, wiki) via lark-cli, run GitNexus code exploration and PR reviews, enforce C/C++ coding standards, generate Rockchip-style technical documents, and process xlsx, docx, and pptx files.
Who are these skills designed for?▼
They target embedded-systems engineers and developers working inside Feishu/Lark-centric organizations, plus maintainers needing strict code review, refactoring, impact analysis, and documentation discipline. The author's background is embedded systems at Nanchang Hangkong University.
What are the runtime prerequisites for the Lark skills?▼
All lark-* skills require the lark-cli binary installed and authenticated. lark-shared handles auth login, logout, identity selection, and permission scopes; lark-doc additionally requires the lark-shared skill, and lark-sheets lists lark-shared as a sibling dependency.
Are these skills open source or licensed?▼
Licensing varies per skill. The xlsx, docx, and pptx skills are proprietary with terms in LICENSE.txt; webapp-testing references its own LICENSE.txt. Most lark-* and gitnexus-* skills declare no explicit license in their frontmatter, so check each skill folder before redistribution.
How do the documentation skills differ from each other?▼
techdoc-writer produces formal deliverables retaining real file names, git diffs, and logs in Rockchip Developer Guide structure, optionally publishing to Feishu docs. reusable-solution-doc produces de-projected, portable generic guides without specific file or library names. write-coding-standards-from-file derives standards from existing source files.