Results for “archive”

Search, post, monitor, and archive on Twitter/X via five tools: the official hosted X MCP server (full-archive search, trends, bookmarks, Articles via xurl bridge), x-search CLI (cost-tracked API v2 research with calendar-day windows, volume counts, multi-query fan-out, feeds, watchlists, posting), xurl (official CLI for any endpoint incl. media/DMs), bird CLI (free session-based reads/writes, frozen at 0.8.0), and Smaug bookmark archival. Triggers on: search tweets, tweets from today, what did X tweet, latest tweets from, tweet volume, expand a Twitter query, check Twitter for, post a tweet, tweet this, post to X, reply on Twitter, full-archive search, what's trending, check mentions, my mentions, timeline, DMs, monitor account, research topic on Twitter, my bookmarks, archive bookmarks.

The English summary is being prepared. Showing the original description.

Use when admins are governing the Chatter group lifecycle — creation policy, public/private/unlisted visibility decisions, group ownership transfer when owners leave, archived vs inactive vs deleted state changes, auto-archive behavior, naming conventions, group templates (Information Templates), and orphan-group cleanup after user terminations. Triggers: 'we have 800 dead chatter groups', 'group owner left the company who owns it now', 'should this group be public private or unlisted', 'when does a chatter group auto-archive', 'how do I delete vs archive a chatter group', 'we need a chatter group naming convention'. NOT for Chatter notification / digest / feed-noise tuning (use admin/chatter-notification-tuning), NOT for Chatter REST API integration patterns (use apex/apex-connect-api-chatter), NOT for Custom Notifications API (use apex/apex-custom-notifications-from-apex), NOT for Experience Cloud / Customer Community group access (different sharing model).

The English summary is being prepared. Showing the original description.

Generate a single-file industrial-archive product landing page (Nordic museum aesthetic, hash-routed detail pages). Takes a natural-language description of one or more "exhibit-style" products (objects, tools, hardware, watches, kitchenware, lighting, audio, instruments, anything with a designed/forged/restrained quality); outputs ONE working .html file. Visitors see a black-framed cover that flips between exhibits, sidebar index, side meta column (material/origin/year/dimension), and click any exhibit → full detail page (giant italic title, spec table, hero image, lead + 3 prose paragraphs, gallery, prev/next). Runs in BOTH Claude Code (writes to ~/Desktop) and GLM / online chat (outputs HTML inline). Trigger: "做个工业风产品落地页", "做克制之物风格的展品页", "industrial-archive-gen ...", or when user drags this skill folder into chat asking for a product page in the Nordic-industrial archive style.

The English summary is being prepared. Showing the original description.

Find usable copies of web pages when normal fetching fails. The skill tries archives and alternative retrieval routes, checks that results contain actual page content, and preserves source details and snapshot dates for citation.

• Finding article copies after a 403 or 429 response
• Recovering archived copies of deleted pages
• Finding API or RSS alternatives to blocked HTML

Audit paginated archives, product lists, and search results. Check canonical tags, which identify each page’s preferred URL, and verify consistent pagination links so search crawlers can reach later pages, including content behind infinite scroll.

• Review canonical tags on blog archive pages
• Check pagination URLs in product lists
• Verify crawlable links for infinite scroll

Retrieve pages blocked by web access filters, read Chinese and social platforms through dedicated tools, and inspect archived copies with their dates. Escalate to browser interaction when simpler extraction methods cannot provide the needed content.

• Read a page that returns a 403 error
• Retrieve posts from Chinese platforms
• Check dated archives of unavailable pages

Trace uploaded files through extraction, conversion, parsing, and reconstruction of saved objects in a CTF sandbox, an isolated competition environment. Preserve original and derived files, distinguish visible validation from backend behavior, and document the smallest reproducible processing chain.

• Trace an uploaded file to its backend effect
• Investigate archive extraction and preview generation
• Compare visible validation with backend file handling

Use OpenViking through OpenClaw to manage long-term memories, search archived conversations, and find imported resources or Agent Skills. Inspect recall traces to understand search results and recover full tool outputs stored outside the conversation.

• Recall past preferences and decisions
• Find exact commands in archived conversations
• Import and search documents or Agent Skills

Capture a public webpage through Latchshot and save a local PNG, JPEG, or PDF. Use viewport images, full-page screenshots, or website thumbnails for reports, visual checks, archives, and social previews.

• Save webpage screenshots for reports
• Capture full pages for visual quality checks
• Archive public webpages as PDFs

Examine Outlook PST and OST archives to extract messages, headers, attachments, and recoverable deleted items. Use the extracted records to trace email routing, reconstruct communication patterns, and support incident investigations or legal evidence review.

• Investigating suspicious emails in Outlook archives
• Tracing message routes through email headers
• Extracting attachments for further analysis

Process large email, document, and transcript archives by routing items to AI models according to their importance. Rule-based privacy checks run before model calls, while extracted information becomes linked knowledge pages with progress checkpoints.

• Extract useful information from large email archives
• Organize decisions and advice from meeting transcripts
• Route reports to suitable models by importance

Populate a new GBrain knowledge base by importing notes, contacts, calendars, email, and other archives in a practical order. Connect people and companies across sources, filter low-value content, and resume interrupted imports from saved progress.

• Choosing what to import after setting up GBrain
• Importing existing Markdown notes or an Obsidian vault
• Connecting contacts with meeting and email history

Turn exported AI chats and agent session logs into dated, searchable pages in gbrain. Check for missing conversations, extract facts, and trace when a topic first appeared or how an idea developed, with quotes and dated references.

• Organizing exported AI chat histories
• Finding the first discussion of a topic
• Tracing how an idea developed

Collect public posts across a blog, newsletter, or feed archive and save clean Markdown pages for each article. The workflow avoids duplicates, supports resumed runs, repairs empty results, and hands articles to a separate enrichment skill.

• Importing a blog's public article archive
• Organizing public newsletter posts as knowledge pages
• Rerunning a feed import without duplicates

Manage skills through conversation: find, inspect, install, edit, remove, and restore them within the current instance. It handles files, repositories, and archives, and can organize documents or images into reusable skills.

• Finding and installing skills from SkillHub
• Importing skills from GitHub or ZIP archives
• Turning documents and images into reusable skills

Keep privacy legal matters organized in separate workspaces for each client or engagement. Record key facts, view matter status, change the active workspace, archive completed matters, or work from practice-wide context without selecting a matter.

• Register a new privacy legal matter
• Review matter status and change active work
• Archive completed matters without deleting records

Organize legal work for multiple clients in separate matter workspaces. Create case records, list their status, switch the active matter, archive completed work, or return to practice-wide context while keeping each engagement’s information separate.

• Create a workspace for a new legal matter
• Check matter status and switch active work
• Archive completed matters with their history

Organize legal work into separate matter folders for different clients or engagements. Create matter profiles, list and switch active matters, archive completed work, or return to practice-level context while keeping matter-specific facts and instructions separate.

• Creating a workspace for a new client engagement
• Switching context between contract matters
• Listing active and archived matters

Analyze rejected plans and reviewer feedback to identify recurring concerns, changing expectations, and concrete prompt improvements. Produce an HTML dashboard from Plannotator archives, or use Claude Code plan rejection reasons when those archives are unavailable.

• Finding recurring reasons for plan rejection
• Understanding how review expectations changed
• Deriving planning instructions from past feedback

Package a completed codebase or project directory as a ZIP archive in a separate final step. Verify that the archive exists, inspect its contents, and report the file location with a brief contents summary.

• Delivering a completed codebase as a ZIP file
• Packaging projects for download
• Archiving deliverables containing multiple files

Package project files into a ZIP archive and verify that the deliverable exists and is not empty before completing a task. It also defines a fallback for archiving available files when the agent approaches its iteration limit.

• Delivering a code project as a single ZIP file
• Checking that a delivery archive exists and is not empty
• Reviewing files before packaging a project

Inspect BB storage across machines, identify cleanup candidates, and remove archived files or unused development data. Configure automatic thread archiving and deletion, with previews showing how many threads would be affected before saving retention settings.

• Find threads and files using the most storage
• Clean up files from archived threads
• Remove development data for deleted checkouts

Search tasks in todos.json and its archive by ID, title, keywords, status, priority, or assignee. Results can show a concise task list or full details, with options to search archived tasks alone or include all tasks.

• Finding a task by its exact ID
• Searching task titles, content, and links
• Finding tasks by status, priority, or assignee

Build, validate, and release Marina applications and reports, then load or query their Postgres data. Manage application revisions, preview changes locally, roll back to retained packages, or archive applications through the Marina command line.

• Build and publish a Marina report or application
• Preview application changes with local Postgres
• Load tables and inspect data with SQL